Skip to content
Codebase Memory MCP

Codebase Memory MCP

by DeusData
Released
MIT
Repository
Developer ToolsDatabases & Data

Summary

Local code-intelligence MCP server that indexes a repository into a persistent knowledge graph, so structural questions cost one query instead of a file-reading spree.

Features

  • Persistent code knowledge graph queried with Cypher-like syntax
  • Tree-sitter parsing across 158 languages, hybrid LSP typing for 12
  • Sub-millisecond structural queries; ~99% fewer tokens than file crawling
  • Single static binary — no Docker, no API keys, no telemetry
  • Installer auto-configures Claude Code and Cursor

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Codebase Memory MCP" tools will be available.
{
  "mcpServers": {
    "codebase-memory-mcp": {
      "command": "codebase-memory-mcp",
      "args": []
    }
  }
}

Description

Ask an agent "who calls this function" and it will grep, open twenty files and burn six figures of tokens arriving at an answer a compiler would know instantly. Codebase Memory MCP replaces that with a graph: it indexes the repository once into nodes (functions, classes, routes) and edges (CALLS, IMPORTS, HTTP_CALLS) and answers structural queries in under a millisecond.

The indexing is two-layer. Tree-sitter provides fast syntactic parsing across 158 vendored grammars, pulling out definitions, imports and call sites. On top of that a hybrid LSP layer does type-aware refinement for a dozen languages — Python, TypeScript/JavaScript, PHP, C#, Go, C, C++, Java, Kotlin, Rust and Perl — resolving types across files without actually running a language server. Results are held in SQLite with LZ4 compression and written out in a single dump. A daemon coordinates sessions across multiple agents, runs background watchers and serves an optional graph visualisation on localhost.

The project's own measurement of the payoff: five graph queries consumed roughly 3,400 tokens where file-by-file exploration of the same question took about 412,000. It reports full-indexing an average repository in milliseconds and the Linux kernel — 28M lines across 75,000 files — in about three minutes.

It is a single static binary with no runtime dependencies, no Docker, no API keys and no telemetry; everything is local and code never leaves the machine. macOS, Linux and Windows builds are published, and the installer auto-detects Claude Code and Cursor and wires them up. MIT licensed.

Related MCP Servers

MCP: Codanna

by Codanna

Local code intelligence MCP server that returns symbol context, call graphs and impact analysis in a single call — 15 languages, indexed on your own machine.

Developer Tools

MCP: Graphicle

by Graphicle

Local-first Rust MCP server that maps your repo into a code graph and project memory, then hands coding agents cited file-and-line excerpts.

Developer Tools

MCP: agentmemory

by rohitg00

Self-hosted persistent memory for coding agents: hooks capture what you do, and an MCP server lets any agent recall it across sessions and across tools.

Databases & Data

MCP: Graft

by Trail

Featured

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

Developer Tools
Browse all MCP servers →