Connect your coding agent

Graphide gives a coding agent the map through an MCP server. With it the agent asks the map who calls a function, what a change would break, or where something is, in one call instead of a dozen searches.

There are three ways to connect one. All of them need you signed in to Graphide (gr login). The agent itself runs on its own sign-in: what you use in Claude Code or Codex is billed by Anthropic or OpenAI.

In the app

Agents you start in the app, Claude Code or Codex, already have the map. Nothing to set up. See Agents in the app.

In your terminal, writing nothing

gr claude        # Claude Code
gr codex         # Codex

gr claude runs Claude Code with Graphide’s hooks, permissions, MCP server and skill passed on its command line. gr codex runs Codex with Graphide’s MCP server passed the same way. Neither writes anything to your project or to the agent’s own settings, so there is nothing to undo.

Every argument goes on to the agent, so gr claude --resume or gr codex exec "…" work as they would without gr. For the agents’ own help use gr help claude, since gr claude --help prints Claude Code’s.

In your terminal, installed into the project

For an agent you start some other way, or one gr does not launch, gr harness install writes the connection into the project:

gr harness list              # which agents are found here, and what is installed
gr harness install cursor
gr harness status cursor
gr harness uninstall cursor  # take Graphide's part out again

Agent	Name	What it writes
Claude Code	claude	Hooks in .claude/settings.local.json, a skill, and the MCP server
Codex	codex	A block in AGENTS.md. The MCP server is never written; run gr codex for it
Cursor	cursor	.cursor/mcp.json and .cursor/rules/graphide.mdc
Gemini CLI	gemini	.gemini/settings.json and a block in GEMINI.md
OpenCode	opencode	opencode.json and a block in AGENTS.md
VS Code (Copilot agent mode)	vscode	.vscode/mcp.json and a block in .github/copilot-instructions.md
Windsurf	windsurf	Windsurf’s MCP config for your user, and a block in .windsurfrules

Before it writes, gr harness install backs up each file it changes, and it adds the new MCP files to the repository’s git exclude so you do not commit them by accident. It changes only Graphide’s own part of a shared file such as AGENTS.md. If you are signed out it writes nothing.

After installing, some agents need one more step, which gr harness install prints:

• Cursor: cursor-agent mcp enable graphide, or turn the server on in Cursor’s MCP settings.
• Gemini CLI and VS Code: trust the workspace.
• Windsurf Enterprise: turn MCP on in Cascade’s settings.

gr harness uninstall <agent> --all removes the connection from every project on this computer that has it.

What the agent gets

The MCP server answers from the map the daemon keeps. It has no tools for the shell, the web, git or editing files: the agent keeps using its own for those. If you sign out, its tools answer that they are locked and name gr login.

The map’s tools include:

Tool	Answers
query	A question about the code, as a small ranked slice of the map in one call
impact	Who calls a symbol and what a change to it breaks, hop by hop with file:line
search_nodes	Parts of the map by name, path or description
get_node_code	One part’s source
find_path	Whether one part can reach another
similar	Code that does something similar
resolve_location	Which part of the map owns a file:line
get_node_diff	What changed about a part between two revisions
switch_root	Moves the session to another worktree of the same repository
report_issue	Sends a Graphide bug the agent ran into to the Graphide team

Each agent starts with a small set of these, chosen for that agent, so the server costs little of its context.

The same answers are on the command line, for you or for scripts:

gr query "where are sessions refreshed"
gr impact internal/auth/session.go:Refresh
gr code internal/auth/session.go:Refresh
gr outline internal/auth/session.go

See the command reference for each.

Another MCP client

gr mcp is the server itself, over stdio, for any MCP client gr harness does not list. Point the client at gr mcp as a stdio server, started in the project’s folder. It is not a command to run by hand.