Setup and Safety

Connect to Forge MCP

Use one remote endpoint to access the Forge tools, resources, and prompts allowed by your current account authority.

Remote MCP Endpoint

https://forge.thevikingstack.com/mcp

Copy this exact HTTPS URL. Do not add an SSE path, credentials, query parameters, or a session identifier.

Connect Claude.ai

Team and Enterprise Owners

Open Organization Settings → Connectors → Add → Custom → Web. Enter https://forge.thevikingstack.com/mcp, then choose Add.

Team and Enterprise Members

After an owner configures Forge MCP, open Customize → Connectors, find Forge MCP, then choose Connect.

Individual Plans

Open Customize → Connectors → + → Add Custom Connector. Enter https://forge.thevikingstack.com/mcp, add it, then choose Connect.

Complete the browser sign-in and review the Forge consent screen before choosing an authorized account or the distinct platform-owner grant. In a conversation, use + → Connectors to toggle the whole Forge MCP connector for that conversation. Under Search and tools, disable any individual Forge tools that the task does not need.

See Anthropic's Custom Connectors Guide (opens in a new tab) if client controls have moved.

Connect Codex

Add Forge as a remote HTTP MCP server, then begin OAuth sign-in:

codex mcp add forge --url https://forge.thevikingstack.com/mcp
codex mcp login forge
codex mcp list

Finish authorization in the browser. Review the consent kind and select the account you intend Codex to use. Runcodex mcp list to confirm the configured server.

For current client controls, see the Codex MCP Guide (opens in a new tab).

Choose the Right Grant

Account Grant

Choose an active Forge-entitled account during consent. The grant stays bound to that account. Current membership, role, entitlement, and Forge MCP controls are checked again on every request.

Platform Owner Grant

Available only to a verified platform owner. It starts without a customer account. Use forge_context_set to choose an authorized account and receive an opaque context handle.

Platform calls for customer data must include the context handle. Forge reauthorizes it on every use; it expires after 12 idle hours or 24 total hours. Treat it as private temporary connection data and do not paste it into tickets, logs, or screenshots.

Review Writes Before Approval

Forge reads project, asset, connection, and AEO metadata. It does not return secrets, provider tokens, or stored asset bodies. The only account writes are bounded project and draft-asset creation for an account admin, owner, or authorized platform context. Provisioning is platform-owner only.

Every write requires client approval and a caller-supplied operation key. Read the proposed tool name and inputs before approving it; never ask a client to bypass Forge authorization or expose credentials.

Revoke or Reconnect

To stop a grant from Forge, sign in and open Connections, then revoke the connected client.
You can also disconnect Forge in the client. Revoking in Forge stops the Forge grant and its tokens even if the client still shows the connector configuration.
To use another account, revoke the account-bound grant and connect again. An existing ordinary grant cannot be moved between accounts.
If authorization becomes stale, disconnect or log out in the client, then run the connection flow again instead of copying tokens manually.

Safe Troubleshooting

Authorization Denied: Confirm that you are signed in, your account is active and Forge-entitled, and your current role permits the requested tool.
Context Unavailable: Platform owners should set context again. Context handles expire and cannot be reused by another actor, client, or grant.
Connector Stopped: Check whether the account or global MCP service control is disabled, then reconnect only after an authorized owner restores access.
Safe Evidence: Keep the safe error code and request ID. Never capture access tokens, refresh tokens, secrets, asset bodies, or context handles.

Claude Code (Optional)

Claude Code is documented for convenience but is not a Forge MCP launch gate. Add the same stateless HTTP endpoint and authorize through its MCP menu:

claude mcp add --transport http forge https://forge.thevikingstack.com/mcp
# Start Claude Code, then open:
/mcp

Follow the browser OAuth flow. Do not add authorization headers or paste a token into the command.