Graphify MCP: connect your coding agent

Graphify MCP is the hosted Model Context Protocol server for your indexed repositories. Your coding agent queries the same code graph you see in the console: find symbols, follow callers, check impact, recall team memory, and read review status. Nothing runs on your machine. Sign in with OAuth. There is no API key to paste.

https://api.graphify.com/mcp


Transport	Streamable HTTP
Auth	OAuth (browser sign-in, PKCE). No API key in the URL or config.
Scope	`graphify:query`
When to use it	This server. Use the local MCP server for an offline or on-machine graph.

Main setup lives in the console under Connectors → MCP. That page fills in the endpoint, shows Agent connection status, and offers starter tasks under Try it on your repository once a repository is indexed.

You need a Graphify account at app.graphify.com, at least one indexed repository, and an MCP client that supports remote HTTP servers. Hosted Graphify lists 63 grammars.

Connect your client

One-click installs: Connect Graphify in Claude for Claude.ai and Desktop or Claude Code, Connect to Cursor, the Graphify extension for VS Code, or the Graphify plugin for ChatGPT and Codex.

Graphify is a connector in Anthropic’s Connectors directory. Full setup is on two pages.

Surface	Guide
Claude.ai, Desktop, mobile	Graphify for Claude
Claude Code	Account bridge, manual MCP, and project config

Endpoint: https://api.graphify.com/mcp. Streamable HTTP. OAuth only. There is no API key.

codex mcp add graphify --url https://api.graphify.com/mcp
codex mcp login graphify

The login step is required. Without it, Graphify rejects the connection.

~/.cursor/mcp.json

{
  "mcpServers": {
    "graphify": {
      "url": "https://api.graphify.com/mcp"
    }
  }
}

Use .cursor/mcp.json to scope it to one repository. Cursor shows Needs login until you finish the one-time sign-in.

copilot mcp add --transport http graphify https://api.graphify.com/mcp

Copilot CLI signs in on first connect. If you edit ~/.copilot/mcp-config.json by hand, include "tools": ["*"], or the tools stay unavailable to the model.

Run MCP: Add Server from the Command Palette, choose HTTP, enter https://api.graphify.com/mcp, and name it graphify. Or add .vscode/mcp.json:

.vscode/mcp.json

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

VS Code uses servers, not mcpServers. Finish the browser sign-in when prompted. No token goes in this file.

gemini mcp add --transport http graphify https://api.graphify.com/mcp

Or add it to ~/.gemini/settings.json. Gemini CLI uses httpUrl for remote servers, not url:

~/.gemini/settings.json

{
  "mcpServers": {
    "graphify": {
      "httpUrl": "https://api.graphify.com/mcp"
    }
  }
}

On first use, Gemini CLI opens a browser sign-in. There’s no key to paste. Use .gemini/settings.json to scope it to one repository.

Graphify also has setup for Windsurf, Cline, Continue, JetBrains, Zed, Goose, Kiro, and other clients, including one-click install links where a client supports them. See Integrations.

Clients without remote OAuth

For a client that only runs local (stdio) servers, use the pinned mcp-remote bridge. It needs Node.js and npm on the client’s PATH, runs the browser sign-in, and stores credentials on your machine:

{
  "mcpServers": {
    "graphify": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.14.3", "https://api.graphify.com/mcp", "--transport", "http-only"]
    }
  }
}

Use your client’s native remote connection when it supports Graphify’s sign-in. The bridge is a third-party package.

Target a repository or group

Add ?repo= with the repository’s full name to set a default:

https://api.graphify.com/mcp?repo=acme/payments

Query a repository group

A combined graph is a query target for your agent, the same way a single repository is.

In the console, open Graphs, choose Combine graphs, and pick the repositories. Wait until the combined graph is ready.
Ask your agent to run list_repositories. Combined graphs appear in that list with kind: "workspace". Their repositoryId is the group id, and fullName is the name you gave the group.
Pass that repositoryId to the usual query tools (find, callers, impact, and the rest). Graphify serves the group’s promoted merged graph.

A group is queryable only when its current merge is promoted. If queryable is false, the merge is still building, failed, or was not promoted. Combined graphs have no pull requests, so review tools do not apply to them. See Graph explorer for how to build and open a combined graph in the console.

What your agent can do

Your client builds its tool list from the server’s tools/list response, so the client’s tool panel always shows the current set. Repository tools such as list_repositories, query_graph, graphify_find, callers, impact, and memory come from the indexed graph. For the job-to-tool map and pasteable prompts, see What your agent can do and Use Graphify from your agent. Graphify also adds these workspace and review tools to every session:

Tool	What it does
`list_workspaces`	Lists the workspaces you belong to and marks the active one. No arguments. Read-only.
`set_workspace`	`handle` (required) switches the session to that workspace. `make_default` (optional) also saves it as your default. State-changing, so most clients ask before running it.
`review_status`	`repository` and `pr_number` are optional. Pass `pr_number` for one PR, or omit it for the 10 most recent reviews. Read-only. Does not start or re-run a review.

Changing workspace changes which repositories the session can see. It doesn’t change your code or the graph.

What `review_status` returns

For one PR, the tool returns a review object (or null with a message if Graphify has not reviewed that PR yet). Without pr_number, it returns a reviews list of up to 10 runs, newest first. Each review includes the repository, PR number and title, status (queued, running, completed, failed, or cancelled), and whether a newer push superseded it. A completed review also includes:

gate: pass or advisory (not a passed field)
Finding counts: blocking_count, advisory_count, and findings_total
top_findings: up to five findings, worst severity first

If the review is still queued or running, the response includes how many minutes it has been in flight and a hint to check again in about 20 to 30 minutes instead of polling continuously. See Pull request reviews. You don’t paste a key. Your client discovers the sign-in flow from the server:

The client’s first request has no token. Graphify answers 401 with a WWW-Authenticate: Bearer resource_metadata="…" header that points at Graphify’s protected-resource metadata.
The client reads that metadata, finds the authorization server, and opens a browser sign-in.
The client exchanges the code for tokens using PKCE. Graphify only supports public clients, so there’s no client secret.
Each refresh rotates the refresh token. A client that reuses an old one is asked to sign in again.

If a token doesn’t verify, you get the same discovery 401, and your client starts the sign-in again.

Server card vs the MCP connection

Your client can find Graphify on its own. Graphify publishes an MCP server card: a small public JSON file that says what the server is and where to connect. A client can read it before it connects or signs in, so you don’t have to type the server URL. The server card is discovery only. It is not the MCP connection, and it does not list your tools. After connect and OAuth, your client gets tools from tools/list. Clients that don’t read server cards keep working with the setup steps above.

Endpoint	What it is
`https://api.graphify.com/mcp/server-card`	Server card: name, icon, remote URL
`https://api.graphify.com/.well-known/ai-catalog.json`	AI catalog entry that points at the card
`https://api.graphify.com/mcp`	The actual MCP endpoint your client calls

What’s in the card

Field	Value
`name`	`io.github.Graphify-Labs/graphify`. Unique ID. Matches the MCP Registry entry.
`title`	`Graphify`. The name a client shows you.
`description`	Search indexed code, trace dependencies, assess change impact, and recall repository memory.
`version`	Version number, such as `0.1.1`. Which release of the listing this is.
`remotes`	`streamable-http` at `https://api.graphify.com/mcp`. Where and how to connect.
`icons`	400×400 PNG logo. The icon a client shows.
`websiteUrl`	`https://graphify.com/mcp`. Where to learn more.
`repository`	`github.com/Graphify-Labs/graphify-mcp`. Where the server code lives.

The AI catalog has one entry, urn:air:graphify.com:mcp:graphify, of type application/mcp-server-card+json, pointing at the server card.

curl -H "Accept: application/mcp-server-card+json" https://api.graphify.com/mcp/server-card

Other discovery endpoints

These public files tell a client how to sign in. Your client reads them for you.

Endpoint	What it describes
`/.well-known/oauth-protected-resource/mcp`	The MCP server, its sign-in server, and the `graphify:query` scope.
`/.well-known/oauth-authorization-server`	Sign-in, token, registration, and revoke URLs, with PKCE (`S256`). Also at `/.well-known/openid-configuration`.

All are on https://api.graphify.com and are cached for an hour.

Why doesn't the card list Graphify's tools?

Your tools depend on your workspace, so a public file can’t list them. Your client gets them from tools/list after you sign in.

Why is there no key or header in the card?

Sign-in uses OAuth. The client finds the sign-in flow from the server’s 401 response, so the card needs no credentials.

Can a web app read the card?

Yes. The card and catalog allow any origin (Access-Control-Allow-Origin: *), are cached for an hour, and send an ETag. Send it back in If-None-Match and you get 304 Not Modified if nothing changed.

Workspaces and MCP sessions

Every request runs in one workspace. Graphify picks it in this order: the workspace bound to this MCP session, then your default workspace, then your only workspace if you belong to just one.

Each client installation gets its own MCP session, so two machines can use different workspaces without overwriting each other.
set_workspace binds the current session. The binding lasts 24 hours by default. With make_default: true, it also becomes your default workspace.
Graphify rechecks your membership on every request. Removed members lose access within 60 seconds.

set_workspace changes state. It changes which workspace, and so which repositories, your agent reads from. It doesn’t change your code or the graph.

Workspace errors

Code	Message
`no_workspace`	”No workspace is selected for this agent.” The message lists your workspaces. Call `set_workspace` with one of them.
`workspace_access_revoked`	”Your access to the bound workspace is no longer valid.” Pick another workspace.
`workspace_not_found`	”That workspace was not found.” Check the handle with `list_workspaces`.
`mcp_session_required`	”set_workspace can only run inside an established MCP session.” Reconnect the client, then retry.
`invalid_arguments`	”set_workspace requires a handle.”

Limits

Limit	Default
Requests	240 per minute
Request body	256 KB

The request limit is counted per client IP address for signed-in sessions. Over the limit returns 429 rate_limited. A request body over 256 KB returns 413 mcp_body_too_large. See Rate limits.

Check the connection

Check the client shows Graphify

Your client should list graphify as connected, with its tools.

List what you can see

Ask your agent:

Use Graphify's list_repositories tool and show the repositories I can access. If the tool fails, report the error instead of guessing.

If you belong to several workspaces, ask it to run list_workspaces, then set_workspace with the one you want.

Ask about code you know

Pick an indexed repository, ask about a function you know, then ask for its callers or tests. Check the evidence against the code.

Seeing the tools doesn’t prove repository access. The last step does. For test prompts per client, see Check your agent is using Graphify.

Fix common problems

What you see	What to do
Needs authentication / Needs login	You are connected, not signed in. Claude Code: `/mcp` → Authenticate. Codex: `codex mcp login graphify`. Cursor and VS Code: finish the browser sign-in.
Verify your email to connect	The account email isn’t verified. Open the verification email, or select Resend the verification email, then connect again. Google or GitHub sign-up: choose that option when you connect.
`list_repositories` is empty	You are in the wrong workspace, or it has no repositories. Switch with `set_workspace`, or index a repository.
A repository returns no results	It is not indexed, or you are in the wrong workspace. Wait for Indexed on Repositories, then confirm the workspace with `list_workspaces`.
Tools connect but chat can’t run them	Turn Graphify tools on in the client, and check that the model can call tools. In Copilot, add `"tools": [""]`. In a Claude chat, select +, then Connectors*, and turn Graphify on.
Graphify is connected but a Claude chat doesn’t use it	The per-chat toggle is off. Turn Graphify on under +, then Connectors. Approve the tool call if Claude asks.
Claude Code `/mcp` doesn’t list the claude.ai connector	Run `/status`. Connectors from claude.ai load only with a Claude account login, not with `ANTHROPIC_API_KEY`, Bedrock, or another provider. Use `claude mcp add`, or `/login` with your Claude account.
Graphify isn’t in my client’s MCP gallery	Gallery listing is separate from the registry. Add `https://api.graphify.com/mcp` directly. Registry id: `io.github.Graphify-Labs/graphify`.
`npx` or Node.js isn’t found	The bridge needs Node. Install Node where the client can find it, or use the client’s native remote setup.
Copilot on github.com can’t connect	No OAuth support there yet. Copilot’s coding agent and code review only support static header credentials, so they can’t use this endpoint yet.
Does Graphify MCP see my local changes?	No. It serves the indexed graph. For uncommitted work, use the local MCP server.

What’s next

Check it's working

Three prompts that prove the agent used Graphify.

What your agent can do

Job-to-tool map and pasteable prompts.

Ask

The same graph, in the console.

Integrations

Setup for each agent.

Try it in Graphify

We build and host the graph for you. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Get started

Core concepts

Features

Workspace

Support

Graphify MCP: connect your coding agent

Connect your client

Clients without remote OAuth

Target a repository or group

Query a repository group

What your agent can do

What `review_status` returns

Server card vs the MCP connection

What’s in the card

Other discovery endpoints

Workspaces and MCP sessions

Workspace errors

Limits

Check the connection

Fix common problems

What’s next

Check it's working

What your agent can do

Ask

Integrations

Try it in Graphify

​Connect your client

​Clients without remote OAuth

​Target a repository or group

​Query a repository group

​What your agent can do

​What review_status returns

​How sign-in works

​Server card vs the MCP connection

​What’s in the card

​Other discovery endpoints

​Workspaces and MCP sessions

​Workspace errors

​Limits

​Check the connection

​Fix common problems

​What’s next

Check it's working

What your agent can do

Ask

Integrations

Try it in Graphify

Connect your client

Clients without remote OAuth

Target a repository or group

Query a repository group

What your agent can do

What `review_status` returns

How sign-in works

Server card vs the MCP connection

What’s in the card

Other discovery endpoints

Workspaces and MCP sessions

Workspace errors

Limits

Check the connection

Fix common problems

What’s next