CodeGraphContext

MCP server by CodeGraphContext

Index local code into a graph database so assistants can query calls, imports, class hierarchies and dependencies.

Runs locally (Runs on your machine: its page has the install command)Runs with uvx

Install CodeGraphContext

Runs on your machine. Your client starts it with this command:

uvx codegraphcontext mcp start

Needs uv (Python) on your computer. The setup steps below show where the command goes in each client.

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/codegraphcontext

About

CodeGraphContext parses local repositories with Tree-sitter or SCIP indexers and stores files, symbols, calls, inheritance and imports in a graph database. An assistant can then query callers, callees, class hierarchies and call chains instead of relying on plain text search. It also ships a CLI with the same indexing and query features, plus file watching to keep the graph current.

It runs locally as a Python package started with uvx, over stdio. No sign-in or API key is needed. An embedded graph database (FalkorDB Lite by default, or KuzuDB) is used out of the box, and Neo4j or other graph backends are optional. The repository must be indexed before it can be queried.

What you can do

  • Index local repositories into a queryable code graph
  • Find callers, callees and call chains across files
  • Explore class hierarchies and import relationships
  • Spot dead code and unexpected dependencies
  • Watch directories and update the graph on changes
  • Load pre-indexed .cgc bundles of well-known repositories

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example prompts

  • Index this repository and show everything that calls the parse_config function.

  • Which modules import the auth package, directly or indirectly?

  • Show the class hierarchy under BaseHandler in this project.

  • Find functions that are never called anywhere in the codebase.

Set up

Every client starts CodeGraphContext on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio codegraphcontext -- uvx codegraphcontext mcp start
  1. Start Claude Code and type /mcp. codegraphcontext should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "codegraphcontext": {
      "command": "uvx",
      "args": [
        "codegraphcontext",
        "mcp",
        "start"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs uv (Python) on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "codegraphcontext": {
      "command": "uvx",
      "args": [
        "codegraphcontext",
        "mcp",
        "start"
      ]
    }
  }
}

Needs uv (Python) on your computer.

VS Code

Or from a terminal:

code --add-mcp '{"name":"codegraphcontext","type":"stdio","command":"uvx","args":["codegraphcontext","mcp","start"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "codegraphcontext": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "codegraphcontext",
        "mcp",
        "start"
      ]
    }
  }
}

Needs uv (Python) on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "codegraphcontext": {
      "command": "uvx",
      "args": [
        "codegraphcontext",
        "mcp",
        "start"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add codegraphcontext -- uvx codegraphcontext mcp start

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.codegraphcontext]
command = "uvx"
args = ["codegraphcontext", "mcp", "start"]

Needs uv (Python) on your computer.

Gemini CLI

gemini mcp add codegraphcontext uvx codegraphcontext mcp start

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "codegraphcontext": {
      "command": "uvx",
      "args": [
        "codegraphcontext",
        "mcp",
        "start"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs uv (Python) on your computer.

FAQ

Can I paste mcp.tc/i/codegraphcontext into my MCP client?

No. CodeGraphContext runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is uvx codegraphcontext mcp start.

Does CodeGraphContext need an API key?

No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.

Is CodeGraphContext a remote or a local server?

Local. Your client starts it as a process on your computer with uvx codegraphcontext mcp start, which needs uv (Python).

What can CodeGraphContext do?

You can index local repositories into a queryable code graph, find callers, callees and call chains across files and explore class hierarchies and import relationships.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc’s robot read CodeGraphContext’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show CodeGraphContext in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![CodeGraphContext on mcp.tc](https://mcp.tc/i/codegraphcontext/badge.svg)](https://mcp.tc/i/codegraphcontext)
HTML
<a href="https://mcp.tc/i/codegraphcontext"><img src="https://mcp.tc/i/codegraphcontext/badge.svg" alt="CodeGraphContext on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/codegraphcontext.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/codegraphcontext" title="CodeGraphContext on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/codegraphcontext.json

What each field means

mcp.tc isn’t affiliated with CodeGraphContext. This page was built from CodeGraphContext’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.