docs(mcp): point a deployed standalone server at FOREST_MCP_SERVER_URL

[Scra3]

Documents FOREST_MCP_SERVER_URL, shipped by agent-nodejs#1832 (merged).

The variable appears in the three places a standalone deployer actually looks:

• the launch command they copy, as the deployed variant
• the environment variable table, marked Required: Yes, when deployed
• the warning in the uploads section, which replaces one saying a deployed standalone server cannot serve remote clients — true before #1832, misleading now

Also closes a gap #26 did not carry: reference/agent-api/nodejs.mdx documents mountAiMcpServer's options with a Since marker each, and fileUploads was in neither the table nor the TypeScript signature, nor requestActionFileUpload in the tool-name list. Versions taken from the changelogs rather than guessed — @forestadmin/agent 1.95.0.

The claim worth reading twice, since it is the one the old warning got wrong: everything a standalone server advertises — the OAuth endpoints a client discovers and the upload URLs of the in-memory store — derives from one base URL the process cannot work out on its own. A storage backend fixes the upload half only, which is why "configure a storage backend" was never a sufficient remedy.

🤖 Generated with Claude Code

Note

Document FOREST_MCP_SERVER_URL requirement for deployed standalone MCP servers

Updates mcp-server.mdx to explain that a deployed standalone server must set FOREST_MCP_SERVER_URL to its public URL, and adds the variable to the environment variables table with notes on when it is required and its default localhost behavior. Also documents the fileUploads option and requestActionFileUpload tool in nodejs.mdx for agent.mountAiMcpServer.

^{Macroscope summarized a20b1f9.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
forest	🟢 Ready	View Preview	Aug 18, 2026, 8:47 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.