A local, queryable map of your codebase for Claude Code: import-aware call graph, durable session memory, and session-history search, exposed as MCP tools.
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":"codemap-mcp","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.
# codegraph A code graph for [Claude Code](https://claude.com/claude-code), served over MCP. It parses your repo into a local SQLite graph, so "who calls this", "what breaks if I change this" and "what did we work out about this last time" are one lookup instead of a search-and-read loop. Python, TypeScript/JavaScript, Vue and Go — including `.vue` `<template>` bindings, where most of a Vue component's methods are actually called from, and Go function literals, where most of a Go test actually lives. [](https://github.com/manoranjan14/codemap-mcp/actions/workflows/tests.yml) [](LICENSE) [](pyproject.toml) ## Install ```bash pipx install "codemap-mcp[server,ts]" codemap-index /path/to/repo cd /path/to/repo claude mcp add --scope local codegraph -- codemap-mcp --repo-root /path/to/repo ``` Start Claude Code in that repo and ask it something you'd normally grep for — *"who calls `useApiClient`?"*, *"what breaks if I change the nav composable?"*. Nothing is written inside your repo; every index lives under `~/.codegraph/`. Re-run `codemap-index` after pulling. It's incremental — well under a second for a no-op on a 4,000-file repo. <details> <summary>Extras, and why there are any</summary> `pip install codemap-mcp` pulls **zero third-party packages**. The indexer and query layer use nothing but the standard library (`ast`, `sqlite3`), and CI asserts that rather than the README claiming it. | extra | brings | needed for | |---|---|---| | `server` | `mcp` | the MCP server — skip it if you only want the CLI | | `ts` | tree-sitter grammars | TypeScript / JavaScript / Vue. Without it those files are skipped with a warning and Python still indexes in full | The `ts` extra installs `tree_sitter_languages` on Python ≤3.12 and `tree-sitter-lan…
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.