MCP — local & hosted

Use ForgeDeck's local and hosted Model Context Protocol servers.

Embed
Preview of the card
<a href="https://docs.forgedeck.net/mcp"><img src="https://docs.forgedeck.net/_api/public/orgs/db9cb8ff-b606-46cf-bbcd-02c8f8a9a3e2/spaces/6f417400-93ca-41a8-a914-df2ae3981dc6/pages/0863ee73-eca7-43aa-a632-975e9284b27b/social-card.svg?v=3e7ae33eec8b" alt="MCP — local &amp; hosted" width="600" height="315"></a>

ForgeDeck speaks the Model Context Protocol (MCP) both locally and in the cloud.

Local MCP server

Out of the box, ForgeDeck can expose a localhost MCP server over Streamable HTTP at /mcp. It's disabled by default — enable it in Settings. Destructive tools are gated behind an explicit opt-in and a confirmation prompt.

Beyond read tools (list projects/tasks/terminals, read a pane, search memory), an MCP client can drive a running agent dynamically: read_terminal to see what it's asking, then prompt_agent (type text) or press_key (answer menus, confirmations, ctrl-c) — the full loop a human would use. Prefer plain HTTP or types? The same surface is available as a REST API with the @forgedeck/sdk client.

Hosted MCP gateway

On Pro and above, ForgeDeck offers a hosted, multi-tenant MCP gateway. Create an API key in your account, then point an MCP client at the gateway with that key as a bearer token:

curl -X POST https://mcp.forgedeck.net/mcp \
  -H "Authorization: Bearer fdk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"forge_list_tools"}'

The gateway authorizes your key against your plan's capabilities — hosted MCP requires the hosted-mcp capability.

Updated