Hosted MCP
Hosted MCP turns a registry version into an MCP server at https://latitude10.tech/mcp/<workspace>/<project>. Each operation in your document becomes a tool, and each tool call an agent makes is one request to your API's host, with the credential you stored.
How it fits together
- The tools come from the version the server serves: the latest, or one you pin.
- Agents connect with an MCP key you hand them, or, on Pro and up, by signing in through your own identity provider.
- Calls go only to a host you've proved is yours, and the agent's own key never reaches your API.
- Agent analytics show which tools are called, by which kind of agent, day by day.
A server that's off answers the same 404 as a project that doesn't exist: “There’s no hosted MCP server here.”
In this section
- Set it up: the base URL, the proof, the credential, the tools, the keys and the switch.
- Refused hosts: the base URLs a server won't call, and why.
- Tool calls: how tools are named, checked and sent.
- Errors: every message an agent can get.
- Keys and allow lists: agents' keys, and which tools each one sees.
- Agent analytics: which tools are called, and by which clients.
- Protocol versions: the MCP versions every endpoint serves.
- OAuth sign-in: people signing in through your identity provider.
Where this comes from
app/hosted-mcp/_lib/server.tsapp/hosted-mcp/_lib/upstream.tsapp/hosted-mcp/_lib/keys.tsapp/mcp/[ws]/[project]/route.ts