Persistent, portable codebase intelligence MCP server with incremental indexing and decision memory
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"codebase-mcp-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# codebase-mcp A local MCP server that gives any AI agent or IDE a persistent, structured understanding of your codebase. It indexes your project once, stores everything in a local SQLite database, and answers structural questions instantly without the agent having to read any files. --- ## The problem it solves Every time you start a new session in Claude Code, Cursor, Cline, or any other AI tool, the agent has to re-read your files to understand the codebase. On large projects this burns thousands of tokens just on orientation, and the agent still only sees a shallow surface. It cannot answer questions like "what calls this function", "what changed since yesterday", or "what decisions were made and why" without reading everything again. codebase-mcp solves this by: - Parsing your code once with tree-sitter (Python, TypeScript, JavaScript, Go, Rust, and 50+ more languages) - Storing every function, class, method, import, and call site in a local database - Keeping that database up to date incrementally (only changed files are re-parsed) - Exposing a set of MCP tools so any agent can query the structure without reading files - Persisting architectural decisions, notes, and session history across every agent and IDE you use --- ## How it is different from standard approaches | | Standard approach | codebase-mcp | |---|---|---| | Codebase understanding | Agent reads files in context window | Pre-indexed, queried via tool calls | | Cost per session | Hundreds to thousands of tokens on orientation | Near zero — index is already built | | Call graph | Not available | Full caller/callee resolution with 3 strategies | | Decisions and notes | Lost when context resets | Stored in database, searchable forever | | Switching agents/IDEs | Start over from scratch | Export once, import anywhere | | Multi-language | Depends on the agent | 50+ languages via tree-sitter | | Incremental updates | Full re-read every time | SHA256-based, only changed files reparsed | The cor…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.