Docs / Set up with your agent

LLMGRAPH for Windsurf

Add the LLMGRAPH MCP server to Windsurf on Windows: the config file, the cmd /c npx form, and how to check it connected.

On this page1 · Add the server to Windsurf 2 · Check that it connected 3 · Sign in once 4 · Make sure Windsurf uses it 5 · The five questions Other agents

Add LLMGRAPH to Windsurf (now Devin Desktop) with one entry in mcp_config.json; if it cannot start npx on Windows, use cmd /c npx -y llmgraph-mcp. This guide follows Windsurf's own docs and is not yet tested by us.

1Add the server to Windsurf

Add from the vendor's docs, not yet tested by us legacy Cascade agent: ~/.config/devin/mcp_config.json (Windows: AppData\Roaming\devin\mcp_config.json). Devin Local agent: devin mcp add, or .devin/mcp_config.json (project) or ~/.config/devin/mcp_config.json (user).

$devin mcp add llmgraph -- npx -y llmgraph-mcp

Or as a file entry:

json

{
  "mcpServers": {
    "llmgraph": {
      "command": "npx",
      "args": [
        "-y",
        "llmgraph-mcp"
      ]
    }
  }
}

The old path ~/.codeium/windsurf/mcp_config.json is not mentioned in the vendor's docs.

Windsurf's own docs do not mention a cmd /c wrapper on Windows. If it cannot start npx, use cmd /c npx -y llmgraph-mcp.

2Check that it connected

Check from the vendor's docs, not yet tested by us (your agent lists them as tools)

Cascade: the ... (Actions) menu of the Cascade panel, MCPs section, lists configured servers and how many tools each has enabled.
Devin CLI: run devin mcp list.

The first time your agent asks a question, LLMGRAPH answers with a sign-in link and a 6-character code. In a terminal you can run this instead:

$npx -y llmgraph-mcp login

The link works for 10 minutes. Open the full link, including everything after the #, sign in with Google, compare the code on the page with the one your agent shows, and approve this device. Approving your first device starts your 7-day trial. The full steps are in Set up with your agent.

4Make sure Windsurf uses it

Adding a server doesn't make an agent use it.

Add a line to your agent's instructions file, AGENTS.md:

AGENTS.md

Before changing code, ask the llmgraph MCP tools who_calls and what_breaks_if_changed; after editing, run check_my_changes; read each answer's label and its lines about what it cannot see.

We can't promise that an agent asks on its own. Every answer starts with llmgraph · : look for it where Windsurf shows what it asked.

5The five questions

Question	What it answers
who_calls	Every place that calls this function, plus calls we can't see.
what_breaks_if_changed	Everything that depends on this, directly or indirectly, and what we can't see.
check_my_changes	After editing: callers you didn't update, and anything we can't see.
what_is_unknown	Where our view is blind (dynamic calls, unknown types, unreadable files) and why.
explain	Why we said this: the evidence behind one answer line.

Other agents

LLMGRAPH for Claude Code: MCP setup on Windows.
LLMGRAPH for Cursor: MCP setup on Windows.
LLMGRAPH for Codex: MCP setup on Windows.
LLMGRAPH for Gemini CLI: MCP setup on Windows.
LLMGRAPH for Antigravity: MCP setup on Windows.
LLMGRAPH for OpenCode: MCP setup on Windows.

Set up with your agentEvery agent on one page, plus the sign-in steps and what to do when something goes wrong.The MCP serverWhat the server answers and what it needs.Questions and answersShort answers to common questions.

For agentsthis page as Markdown/docs/agents/windsurf.mdllms.txt