Graph Indexer for Kilo Code

Graph Indexer for Kilo Code is a local MCP server that gives Kilo Code exact references, call graphs and change impact from an index of your repository. Run npx graph-indexer init and it adds a graph-indexer server to kilo.json or opencode.json, whichever Kilo Code uses in your project.

How do I add Graph Indexer to Kilo Code?

From the repository root, with Node.js 22.5 or later:

npx graph-indexer init

init recognises Kilo Code from kilo.json, kilo.jsonc, a .kilo folder or a .kilocode folder. To force the target, run npx graph-indexer init --agents opencode: Kilo Code shares its init target with OpenCode, because Kilo Code is rebuilt on OpenCode and reads the same configuration.

What does npx graph-indexer init change for Kilo Code?

For Kilo Code, init touches these files:

Use --dry-run to preview and --no-instructions to skip the AGENTS.md block. If the config file contains comments, init does not rewrite it; it prints the entry to paste in instead.

What does the manual Kilo Code configuration look like?

Kilo Code uses the OpenCode format: a mcp object, type local, and the command as one array.

{
  "mcp": {
    "graph-indexer": {
      "type": "local",
      "command": ["npx", "-y", "graph-indexer@3", "serve"],
      "enabled": true
    }
  }
}

Put it in kilo.json if you have one, or in opencode.json. The server indexes the git repository of the directory it starts in, so no --repo is needed.

What does the Kilo Code plugin do?

The Graph Indexer plugin appends short context to the output of Kilo Code’s read, grep, bash, edit and write tools. It queries the repository’s resident Graph Indexer process over a local socket, never the network. It adds where the names in a read are defined once the agent is crawling, where a definition that a search missed lives, and what an edit broke.

Kilo Code can load a plugin from both .kilo/ and .opencode/; the plugin guards against registering twice. If the process does not answer, it adds nothing and starts it in the background for the next call. Install it with npx graph-indexer init --hooks.

What does Kilo Code gain from Graph Indexer?

Kilo Code’s agent gets eight read-only tools. find_references returns every real use of a symbol, grouped by file and enclosing function, with a confidence label. change_impact lists dependents and the tests to run before a signature change. check_changes verifies edits without building.

Against the TypeScript compiler on 400 nestjs symbols, find_references reached 99.7% precision and 96.2% recall; grep reached 12.8% precision (benchmarks). Graph Indexer is not a type checker, and generics, reflection and any are only partly visible. Graph Indexer itself makes no network calls and sends no telemetry; Kilo Code still sends what it reads to its model provider. More in the tools reference and the agents overview.