Codebase knowledge graph MCP server — call chains, topology, and hybrid search for coding agents
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":"orgraph-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.
# orgraph-mcp Codebase knowledge graph for coding agents. Gives Claude Code, Cursor, Codex, and other MCP-compatible agents a persistent graph of any repo — call chains, topology clusters, dependency trees — on top of hybrid code search. ## Quickstart Install [uv](https://docs.astral.sh/uv/getting-started/installation/), then: ```bash uv tool install orgraph-mcp orgraph install ``` `orgraph install` detects installed coding agents and wires up the MCP server automatically. Open any repo in your agent and orgraph starts working — it indexes on first run, no manual setup needed. To undo: `orgraph uninstall` ## What agents can do Once configured, your agent has 6 tools: | Tool | What it does | |---|---| | `search(query)` | Hybrid BM25+semantic search — find code by description | | `trace(symbol, direction, depth)` | Follow call chains forward (`callees`) or backward (`callers`) | | `find_path(from_symbol, to_symbol)` | Shortest call path between two named symbols | | `get_context(file_or_symbol)` | Topology cluster, community, call depth, indegree — where does this fit? | | `find_entry_points(kind)` | HTTP handlers and entry surfaces; `kind = "all" \| "http" \| "topology"` | | `get_dependencies(file, direction, depth)` | Import + call dependency tree, forward or reverse | | `reindex(force)` | Re-index changed/deleted files without restarting the server | The agent picks the right tool automatically based on what you ask. ## Manual usage All commands take a repo path as the last argument. It defaults to `.` so you can omit it when you're already inside the repo. ### Setup ```bash # Build the index (run once, then again after big merges) orgraph index . # Verify the index is healthy — node/edge counts, clusters, communities orgraph status . ``` ### Finding code ```bash # Find code by describing what it does — semantic + keyword search orgraph search "coupon validation logic" . orgraph search "order cancellation refund" . --top-k 5 # List every function…
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.