Skip to content

MCP server

Connect your coding agent to Graphide.

Your agent can set up PR review on your repositories, check how it’s going, and read what each review found, every finding with its evidence.

Server URL

https://mcp.graphide.com

Nothing to install: you sign in once in your browser.

Fastest

Add it to every agent you have

npx -y add-mcp https://mcp.graphide.com --name graphide -g

Finds the agents you have and adds Graphide to each. It needs Node.js. For Claude Desktop and claude.ai, use their Connectors screen instead (below).

The first time your agent uses Graphide, your browser opens: sign in and press Allow.

Or in one click

One agent

Pick your agent

What to copy, where it goes, and how to sign in.

  1. Add Graphide to Claude Code

    Run this in your terminal.

    claude mcp add --scope user --transport http graphide https://mcp.graphide.com

    Or, for everyone on a project, commit this as .mcp.json at its root.

    {
      "mcpServers": {
        "graphide": {
          "type": "http",
          "url": "https://mcp.graphide.com"
        }
      }
    }
  2. Sign in

    Start Claude Code, type /mcp, pick graphide and choose Authenticate. Your browser opens: sign in to Graphide and press Allow.

Watch outIn .mcp.json, "type": "http" is required: without it Claude Code looks for a local command.

Hands off

Or let your agent do it

Read https://graphide.com/setup.md and set me up with Graphide.

Paste this into any coding agent that can run commands. It adds Graphide, opens your browser for you to sign in, then offers to turn on PR review for the repositories you pick.

Check

See that it worked

Ask your agent:

List Graphide’s tools.

It should name these five:

  • review_setupYour next step to turn PR review on
  • review_reposWhich repositories get reviews; turn them on or off
  • review_settingsHow a repository is reviewed
  • review_statusWhat is live, the latest reviews, and why one is waiting
  • review_findingsEverything one PR review found, including what it was not sure enough to post

Graphide CI needs nothing from your agent: it starts by itself once the GitHub App is installed on your organization.

Troubleshooting

If something’s off

Sign in again
  • Claude Code/mcp, pick graphide, then Authenticate
  • Codexcodex mcp login graphide
  • Gemini CLI/mcp auth graphide
  • opencodeopencode mcp auth graphide
  • Ampamp mcp oauth login graphide

In an editor or chat app, press the sign-in or Connect button next to graphide in its MCP settings, or remove Graphide and add it again.

Graphide doesn’t show up

Each agent wants the server under its own keys, and a wrong one is skipped without a word. Check yours, then restart the agent:

  • Claude Code"type": "http"
  • Codex[mcp_servers.graphide]
  • Gemini CLI"httpUrl"
  • opencode"mcp" and "type": "remote"
  • Goosetype: streamable_http and uri:
  • Cursor"url"
  • VS Code"servers" and "type": "http"
  • Windsurf"serverUrl"
  • Zed"context_servers"
  • Cline"type": "streamableHttp"
  • JetBrains"mcp-remote"
No browser opens

Over ssh, in a container or in a cloud agent, there is no browser to open. Add Graphide in the agent on your own computer. Behind a company proxy, your agent needs to reach mcp.graphide.com and your browser graphide.com.

Remove it, or end its access

Remove Graphide from the agent: claude mcp remove graphide --scope user, codex mcp remove graphide, or delete its entry from the file. That leaves its sign-in live. To end its access, sign it out under Connected agents on your dashboard, one agent or all of them: it is refused from its next request, and comes back only if you allow it again.

Every step on this page is also in the docs as plain text: Hosted MCP server.