Forge speaks MCP in both directions. Your agents can call external MCP tools — and another assistant can call a Forge team as one of its tools. That means an assistant you already use can hand real work to a Forge team and read the result back.

Step 1: Create an API key

Go to Settings → API Keys and create one with the scopes you want the calling assistant to have — at minimum runs:write to start runs and outputs:read to read what they produced.

Step 2: Point your MCP client at Forge

Add Forge as an MCP server, authenticating with that key as a Bearer token:

https://forge.shanova.se/api/mcp

Opening that URL in a browser describes the server and lists its tools, which is a quick way to confirm your setup is reaching the right place.

Step 3: Use it

Four tools appear: forge_list_teams to see what the key can run, forge_start_run to hand a team a brief, forge_get_run to check progress, and forge_get_outputs to read the deliverables.

Tip:Runs take minutes, not seconds. A calling assistant should start a run, do something else, and come back to poll — not sit and wait on the first call.

Note:The key's scopes and your monthly run quota apply exactly as they do over the REST API. A key can never do more through MCP than it can directly, so this adds a way in, not a way around.

Use Forge from another AI assistant

Step 1: Create an API key

Step 2: Point your MCP client at Forge

Step 3: Use it

Next steps