Forge MCP
Forge ships an MCP (Model Context Protocol) server that exposes the Forge internal API to AI assistants. Point Claude Code (or Cursor, or Claude Desktop) at it and the assistant can list orgs, query events, aggregate stats, and edit configuration without a copy-paste loop through the dashboard.
It is a single-user server that you run locally. It authenticates with a Personal Access Token (PAT) that you create in the dashboard, and only reaches Forge - nothing else.
Two tools
Section titled “Two tools”forge_help- discovery. Lists the namespaces on the internal API client, methods per namespace and full method signatures. Also exposes aconceptstopic that documents behavioural gotchas not in the OpenAPI spec.forge_evaluate- runs JavaScript in a sandbox whereclientis a pre-authenticatedForgeInternalClient. The assistant composes, filters and aggregates API calls without a round-trip per endpoint.
One evaluator covers the full API surface. Adding new endpoints on the server does not require new MCP tools.
Install
Section titled “Install”The MCP server is published on npm as @codeserk/forge-mcp.
You have two ways to run it:
# global install - simple, but you have to remember to updatenpm install -g @codeserk/forge-mcp
# or let the AI client run it via npx - no install, pinned per config# (use "command": "npx" in the MCP config; see Configure)Tested with Node 20 and 22.
Get a token
Section titled “Get a token”Forge dashboard -> Settings -> Account -> Personal access tokens -> New token. The token is shown once when you create it. If you lose it, revoke it from the same page and create a new one.
Scopes map to HTTP methods:
| Scope | HTTP verb |
|---|---|
read | GET |
create | POST |
update | PUT / PATCH |
delete | DELETE |
Give the token the narrowest scope that fits your use. read is enough to browse; add create to run mutations (including the read-only /evaluate previews, which are POST).
Token-management endpoints are blocked for PAT callers. A PAT can never create or revoke other tokens.