Hosted MCP server

Graphide’s hosted MCP server lets your coding agent set up PR review on your repositories, check how it is going, and read what each review found, every finding with its evidence.

The server is at:

https://mcp.graphide.com

Nothing to install: you sign in once in your browser. graphide.com/mcp has a copy button and an install button for each agent; this page has the same steps as text.

The fastest way

One command finds the agents you have and adds Graphide to each. It needs Node.js:

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

The first time your agent uses Graphide, your browser opens: sign in and press Allow. For Claude Desktop and claude.ai, use their Connectors screen instead (below).

Or in one click: Add to Cursor, Install in VS Code, Install in VS Code Insiders, Add to Goose.

Or paste this into any coding agent that can run commands, and it does all of it, then offers to turn on PR review:

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

In a terminal

Claude Code

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

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

For everyone on a project, commit this as .mcp.json at its root. "type": "http" is required: without it Claude Code looks for a local command.

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

Codex

codex mcp add graphide --url https://mcp.graphide.com

Adding it opens your browser to sign in. If no browser opens, or you added it in the file below, run codex mcp login graphide. The same setup serves the Codex command line and its editor extension.

~/.codex/config.toml; the table is mcp_servers, with an underscore:

[mcp_servers.graphide]
url = "https://mcp.graphide.com"

Gemini CLI

gemini mcp add -s user --transport http graphide https://mcp.graphide.com

Then type /mcp auth graphide in Gemini CLI to sign in.

~/.gemini/settings.json; the key is httpUrl (a plain url means the older SSE transport, which Graphide does not serve):

{
  "mcpServers": {
    "graphide": {
      "httpUrl": "https://mcp.graphide.com"
    }
  }
}

opencode

opencode.json in your project, or ~/.config/opencode/opencode.json for every project. Servers go under mcp, and a server on the web is "type": "remote":

{
  "mcp": {
    "graphide": {
      "type": "remote",
      "url": "https://mcp.graphide.com"
    }
  }
}

Then opencode mcp auth graphide to sign in.

Amp

amp mcp add graphide https://mcp.graphide.com

Then amp mcp oauth login graphide to sign in.

Goose

With Goose Desktop, the Add to Goose link above. Or ~/.config/goose/config.yaml, where the address is uri and the type streamable_http:

extensions:
  graphide:
    enabled: true
    name: graphide
    type: streamable_http
    uri: https://mcp.graphide.com
    timeout: 300

The first time Goose uses Graphide, your browser opens to sign in.

In an editor

Cursor

The Add to Cursor link above, or ~/.cursor/mcp.json (.cursor/mcp.json in one project). Cursor takes just url:

{
  "mcpServers": {
    "graphide": {
      "url": "https://mcp.graphide.com"
    }
  }
}

Then open Cursor Settings, then MCP, and press the sign-in button next to graphide.

VS Code

For GitHub Copilot’s agent mode: the Install in VS Code link above, or:

code --add-mcp '{"name":"graphide","type":"http","url":"https://mcp.graphide.com"}'

For everyone on a project, commit .vscode/mcp.json. Its key is servers, not mcpServers, and it needs "type": "http":

{
  "servers": {
    "graphide": {
      "type": "http",
      "url": "https://mcp.graphide.com"
    }
  }
}

When VS Code asks whether graphide may sign in, choose Allow. If it doesn’t ask, run MCP: List Servers from the Command Palette and start graphide.

Windsurf

~/.codeium/windsurf/mcp_config.json (newer versions: ~/.config/devin/mcp_config.json), then refresh Cascade’s MCP list. The key is serverUrl:

{
  "mcpServers": {
    "graphide": {
      "serverUrl": "https://mcp.graphide.com"
    }
  }
}

Zed

In Zed’s settings (zed: open settings); servers go under context_servers:

{
  "context_servers": {
    "graphide": {
      "url": "https://mcp.graphide.com"
    }
  }
}

Cline

In Cline, MCP Servers, then Configure, opens cline_mcp_settings.json. Without "type": "streamableHttp" Cline tries the older SSE transport:

{
  "mcpServers": {
    "graphide": {
      "type": "streamableHttp",
      "url": "https://mcp.graphide.com"
    }
  }
}

With the Cline command line:

cline mcp add graphide https://mcp.graphide.com --transport http

JetBrains

AI Assistant cannot sign in to a server on the web, so it runs mcp-remote, a small bridge that can, through Node.js. In Settings → Tools → AI Assistant → Model Context Protocol (MCP), press Add and paste:

{
  "mcpServers": {
    "graphide": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.graphide.com"
      ]
    }
  }
}

In a chat app

• Claude Desktop: Settings → Connectors → Add custom connector. Name it Graphide, paste https://mcp.graphide.com, then press Connect and sign in. Never put a url entry in claude_desktop_config.json: that file takes only programs on your computer, and a web address can break it.
• claude.ai: Customize → Connectors → Add custom connector, the same way. The free plan allows one custom connector; on a Team or Enterprise plan an owner adds it first, in Organization settings.
• ChatGPT: in Settings → Security and login, turn on Developer mode. Then Plugins → Add → Create: name it Graphide, paste the address and choose OAuth.

Any other agent

Add a server named graphide of type Streamable HTTP (some apps say HTTP) at https://mcp.graphide.com. It signs in with OAuth and PKCE and registers itself, so there is no client ID, token or Authorization header to paste. Most apps that keep servers in a JSON file read this:

{
  "mcpServers": {
    "graphide": {
      "url": "https://mcp.graphide.com"
    }
  }
}

An app that runs only programs on your computer, or cannot sign in itself, can run mcp-remote, which needs Node.js:

npx -y mcp-remote https://mcp.graphide.com

Check it worked

Ask your agent to list Graphide’s tools. It should name review_setup, review_repos, review_settings, review_status and review_findings.

For Graphide CI it also has ci_status and ci_switch: ask your agent to get you on Graphide CI, and it switches the repositories you say yes to (For coding agents).

If something’s off

• Sign in again: in Claude Code, /mcp, pick graphide, then Authenticate; codex mcp login graphide; in Gemini CLI, /mcp auth graphide; opencode mcp auth graphide; amp mcp oauth login graphide. In an editor or chat app, press the sign-in or Connect button next to graphide, or remove Graphide and add it again.
• Graphide doesn’t show up: a wrong key is skipped without a word. Check the keys above for your agent (servers against mcpServers, url, serverUrl, httpUrl, uri, type), then restart the agent.
• No browser opens: over ssh, in a container or in a cloud agent there is no browser. 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 it from the agent with claude mcp remove graphide --scope user, codex mcp remove graphide, or delete its entry. 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.