# Koragraph

Indexes every repo you point it at into one local graph, so your agent can see what a change will break. Remembers facts tied to the code itself.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 14
- Author: Koragraph
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Koragraph/KoragraphMCP
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/mcp/koragraph

## What it does

Point Koragraph at a set of repositories and it builds a single graph from them: services, files, endpoints, tables, and the calls that actually connect them. Call edges are resolved from the syntax tree instead of guessed by name, and edges that span two repos show up too.

The memory layer stores what your agent learned — fixes for failures, rules, corrections — on your machine, attached to a declaration rather than a line number. Rename the declaration and the note follows it. Delete the declaration and the note retires. No hand-kept `CLAUDE.md` file is involved.

Setup takes three steps: `npm install -g koragraphmcp`, then `koragraph ingest /path/to/repo`, then `claude mcp add koragraph -- npx -y koragraphmcp`. Node.js 22 or newer is required. One more step gets the memory going: tell your agent in the project to read `KORAINIT.md` and do what it says. Skip it and only the graph tools work.

You can call the tools over MCP or straight from a shell, for instance `koragraph blast src/pay.js`. Both routes hit the same graph. Results come back as `file:line` pointers, and exactly one tool writes to memory.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add koragraph -- npx -y koragraphmcp
```

### Codex

**Platform CLI**
```bash
codex mcp add koragraph -- npx -y koragraphmcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "koragraph": {
            "command": "npx",
            "args": [
                "-y",
                "koragraphmcp"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "koragraph": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "koragraphmcp"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add koragraph npx -y koragraphmcp
```

## When to use it
- check what depends on a file before editing it
- trace callers of a symbol across several repositories
- keep agent notes about bugs and fixes attached to the code they concern
- carry project rules into later sessions without a hand-written context file
- see which symbols tend to change together

## Example prompts
- Set up koragraph for this repo, index it, and report how many nodes and edges you got
- Show me what depends on `src/pay.js` and which parts have no test coverage
- Read `KORAINIT.md` and follow it, then tell me what it changed

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md