shapes, which says where every RPC, table and handler is with its file and line. Use this when your agent works in an editor rather than a Reliant chat.
forge agent mcp runs the same commands in process and answers over stdio, so a tool call and the CLI give the same result. In a Reliant chat you need none of this: the agent’s shell already has reliant forge, signed in. Why this helps an agent covers the wider design.
Before you begin
- Claude Code or Cursor.
- Node 18 or later for
npx -y @reliantlabs/forge agent mcp, which downloads the matching Forge binary the first time it runs. If you have Reliant installed,reliant forge agent mcpis the same server and needs no download. - For telemetry tools, a Reliant account with a deployed project (see the last step).
1
Add the server to Claude Code
From your repo:With Reliant installed,
terminal
claude mcp add forge -- reliant forge agent mcp does the same with the Forge Reliant ships. The server acts on the directory it starts in, and every tool except explain_error also takes a dir argument, so the agent can point it at another repo.2
Or add it to Cursor
Put this in
.cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them:.cursor/mcp.json
3
Check the server answers
In Claude Code,
/mcp lists the server and its tools. To see exactly what an editor receives, send the MCP handshake yourself. This is the result of an initialize then tools/list over stdio to npx -y @reliantlabs/forge agent mcp:Output (trimmed)
ro=False marks the tools that change something, so your editor asks before calling them. The server’s instructions tell the model what Forge is and to load the forge skill first (adopt in a repo that is not a Forge project yet). reliant forge agent mcp on Reliant v1.21.3 returned the same 16 tools.4
Ask it something
Ask the agent where the task API lives. It calls Every line ends in a file and line, so the agent’s next step is one targeted read instead of a search. Outside a Forge project,
shapes with grep: "Task", which returned this on a Go API project:Output (trimmed)
benefits is the first call: it says what Forge does for that repo as it stands.5
Add the hosted connector for telemetry
The local server has no telemetry tools. Errors, logs, traces and release checks for your deployed environments come from the hosted Reliant Forge connector (In Claude Code, run
obs_status, obs_issues, obs_issue, obs_logs, obs_traces, obs_check and more), and it needs you signed in:terminal
/mcp, pick reliant-forge and choose Authenticate. In Cursor, add "reliant-forge": {"url": "https://api.reliantapi.com/forge/mcp"} under mcpServers and click Needs login. Before sign-in the endpoint answers 401 and points the client at its OAuth metadata. Debug production with an AI agent uses both servers together.What this does not do
- No monitoring without signing in. The hosted connector works only for a signed-in person, and only on the organization and projects you grant it. There is no anonymous path to your telemetry.
- No telemetry from the local server. It works on the repo: skills, introspection, lint, generate. Use both servers if you want both.
deploy_claimableis for no account. It puts a Vite or Next.js app live with a claim link, and is refused while you are signed in. Signed-in deploys arereliant forge env deploy(Deploy a static site with a CDN).
Troubleshooting
⚠️ this forge is v1.8.0, but forge.yaml pins forge_version ... — a different forge than the project's.
⚠️ this forge is v1.8.0, but forge.yaml pins forge_version ... — a different forge than the project's.
The server does not hand off to the Forge your project pins. It reports the skew at the top of the result and still answers. To match the pin, point the server at the command the warning prints, such as
go run github.com/reliant-labs/forge/cmd/forge@<pinned version> mcp.A 403 that names a consent URL (hosted connector)
A 403 that names a consent URL (hosted connector)
You signed in but have not chosen what the connector may read. Open the URL, pick the organization and projects, and retry.
Next steps
Debug production with an AI agent
Follow one failing request from the error to the line, with the hosted tools.
Adopt an existing Vite or Next.js app
Make your app a Forge project in place, with browser logs on disk.
Why this helps an agent
Exit codes, skills from the binary, and
shapes.MCP servers in Reliant
Add any MCP server to Reliant’s own agents.