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.comNothing 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 -gFinds 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.
Add Graphide to Claude Code
Run this in your terminal.
claude mcp add --scope user --transport http graphide https://mcp.graphide.comOr, for everyone on a project, commit this as
.mcp.jsonat its root.{ "mcpServers": { "graphide": { "type": "http", "url": "https://mcp.graphide.com" } } }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.
Add Graphide to Codex
Run this in your terminal. It serves the Codex command line and its editor extension.
codex mcp add graphide --url https://mcp.graphide.comOr add it to
~/.codex/config.toml.[mcp_servers.graphide] url = "https://mcp.graphide.com"Sign in
Adding it opens your browser: sign in to Graphide and press Allow. If no browser opens, or you edited config.toml, run
codex mcp login graphide.
Watch outThe table is mcp_servers, with an underscore: Codex ignores mcpServers and mcp-servers.
Add Graphide to Gemini CLI
Run this in your terminal.
gemini mcp add -s user --transport http graphide https://mcp.graphide.comOr add it to
~/.gemini/settings.json.{ "mcpServers": { "graphide": { "httpUrl": "https://mcp.graphide.com" } } }Sign in
In Gemini CLI, type
/mcp auth graphide. Your browser opens: sign in to Graphide and press Allow.
Watch outThe key is httpUrl. A plain url means the older SSE transport, which Graphide does not serve.
Add Graphide to opencode
Add this to
opencode.jsonin your project, or to~/.config/opencode/opencode.jsonfor every project.{ "mcp": { "graphide": { "type": "remote", "url": "https://mcp.graphide.com" } } }Sign in
Run
opencode mcp auth graphide. Your browser opens: sign in to Graphide and press Allow.
Watch outopencode keeps servers under mcp, and a server on the web has "type": "remote", not "http".
Add Graphide to Amp
Run this in your terminal.
amp mcp add graphide https://mcp.graphide.comSign in
Run
amp mcp oauth login graphide. Your browser opens: sign in to Graphide and press Allow.
Add Graphide to Goose
With Goose Desktop installed, press the button.
Or add it to
~/.config/goose/config.yaml.extensions: graphide: enabled: true name: graphide type: streamable_http uri: https://mcp.graphide.com timeout: 300Sign in
The first time Goose uses Graphide, your browser opens: sign in and press Allow.
Watch outGoose names the address uri, not url, and the type streamable_http.
Sign in
Open Cursor Settings, then MCP, and press the sign-in button next to graphide. Your browser opens: sign in to Graphide and press Allow.
Watch outCursor’s file takes just url: no type, no serverUrl.
Add Graphide to VS Code
For GitHub Copilot’s agent mode. Press the button, then Install in VS Code.
Or run this in your terminal.
code --add-mcp '{"name":"graphide","type":"http","url":"https://mcp.graphide.com"}'Or, for everyone on a project, commit this as
.vscode/mcp.json.{ "servers": { "graphide": { "type": "http", "url": "https://mcp.graphide.com" } } }Sign in
When VS Code asks whether graphide may sign in, choose Allow. Your browser opens: sign in to Graphide and press Allow. If it doesn’t ask, run MCP: List Servers from the Command Palette and start graphide.
Watch outVS Code’s file uses servers, not mcpServers, and needs "type": "http".
Add Graphide to Windsurf
Add this to
~/.codeium/windsurf/mcp_config.json(newer versions:~/.config/devin/mcp_config.json), then refresh Cascade’s MCP list.{ "mcpServers": { "graphide": { "serverUrl": "https://mcp.graphide.com" } } }Sign in
When Windsurf connects to graphide, your browser opens: sign in and press Allow.
Watch outWindsurf’s key is serverUrl, not url.
Add Graphide to Zed
Open Zed’s settings (
zed: open settings) and add this.settings.json
{ "context_servers": { "graphide": { "url": "https://mcp.graphide.com" } } }Sign in
When Zed starts graphide, your browser opens: sign in and press Allow.
Watch outZed keeps servers under context_servers, not mcpServers.
Add Graphide to Cline
In Cline, open MCP Servers, then Configure, and add this to
cline_mcp_settings.json.{ "mcpServers": { "graphide": { "type": "streamableHttp", "url": "https://mcp.graphide.com" } } }Or, with the Cline command line, run this.
cline mcp add graphide https://mcp.graphide.com --transport httpSign in
When Cline connects to graphide, your browser opens: sign in and press Allow.
Watch outLeave out "type": "streamableHttp" and Cline tries the older SSE transport.
Add Graphide to JetBrains
In Settings → Tools → AI Assistant → Model Context Protocol (MCP), press Add and paste this.
{ "mcpServers": { "graphide": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.graphide.com" ] } } }Sign in
The first time AI Assistant starts graphide, your browser opens: sign in and press Allow.
Watch outAI Assistant cannot sign in to a server on the web, so this runs mcp-remote, a small bridge that can, through Node.js.
Add Graphide to Claude Desktop
Open Settings → Connectors → Add custom connector. Name it Graphide and paste this address.
https://mcp.graphide.comSign in
Press Connect next to Graphide. Your browser opens: sign in to Graphide and press Allow.
Watch outNever put a url entry in claude_desktop_config.json: that file takes only programs on your computer, and a web address can break it.
Add Graphide to claude.ai
Open Customize → Connectors → Add custom connector. Name it Graphide and paste this address.
https://mcp.graphide.comSign in
Press Connect next to Graphide. Your browser opens: sign in to Graphide and press Allow.
Watch outThe free plan allows one custom connector. On a Team or Enterprise plan, an owner adds it first, in Organization settings.
Add Graphide to ChatGPT
In Settings → Security and login, turn on Developer mode. Then Plugins → Add → Create: name it Graphide, paste this address and choose OAuth.
https://mcp.graphide.comSign in
ChatGPT opens Graphide’s sign-in: sign in and press Allow.
Watch outWithout Developer mode there is no Create button: it is how ChatGPT lets you add your own server.
Add Graphide to Other
Add a server named graphide of type Streamable HTTP (some apps say HTTP) at this address. Most apps that keep servers in a JSON file read this.
{ "mcpServers": { "graphide": { "url": "https://mcp.graphide.com" } } }If your app runs only programs on your computer, or cannot sign in itself, have it run mcp-remote, which needs Node.js.
npx -y mcp-remote https://mcp.graphide.comSign in
Your app should open your browser to sign in (OAuth with PKCE; it registers itself, so there is no client ID to enter). Sign in and press Allow.
Watch outThere is no token or Authorization header to paste: signing in takes its place.
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 onreview_reposWhich repositories get reviews; turn them on or offreview_settingsHow a repository is reviewedreview_statusWhat is live, the latest reviews, and why one is waitingreview_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 - Codex
codex mcp login graphide - Gemini CLI
/mcp auth graphide - opencode
opencode mcp auth graphide - Amp
amp 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.
- Claude Code
- 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" - Goose
type: streamable_httpanduri: - Cursor
"url" - VS Code
"servers"and"type": "http" - Windsurf
"serverUrl" - Zed
"context_servers" - Cline
"type": "streamableHttp" - JetBrains
"mcp-remote"
- Claude Code
- 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.