What runtime does Graphlens Mcp require?
Python ≥ 3.13 (a constraint inherited from the `graphlens` engine). Additional toolchains (Node for TypeScript, Go toolchain, etc.) are needed for full cross‑file semantics in those languages.
@Neko1313
Basic information
Model Context Protocol (MCP) server for Graphlens. Exposes polyglot code graphs to LLM agents.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"graphlens": {
"command": "graphlens-mcp",
"args": [
"serve",
"--db",
"/home/neko/project/graphlens/.graphlens/graph.db",
"--root",
"/home/neko/project/graphlens"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Graphlens Mcp is a free, MIT‑licensed MCP server that gives coding agents a semantic code graph of a project — symbols, cross‑file calls, references, imports and cross‑language boundaries. It builds on the language’s own LSP‑grade analysis engines (rust‑analyzer, gopls, the TypeScript compiler, the bundled ty engine for Python) to produce a stable, real picture of the codebase.
Install with uv tool install graphlens-mcp (requires Python ≥ 3.13), then run graphlens-mcp init inside your project to detect languages, index the code, and configure your agent. Restart the agent (Claude Code, Cursor, etc.) and ask structural questions like “what breaks if I change the signature of create_order?”. The server is launched automatically by the agent; you can also use status, reindex, and remove commands.
search (find by name/content/meaning), relations (neighbourhood of a symbol), info (read source or file outline).<project>/.graphlens/graph.db).Python ≥ 3.13 (a constraint inherited from the `graphlens` engine). Additional toolchains (Node for TypeScript, Go toolchain, etc.) are needed for full cross‑file semantics in those languages.
A filesystem watcher (started by `serve`) re‑indexes the connected set — the changed file plus its direct importers and imports — on every edit. At startup, a one‑shot reconcile scans the project to handle changes made while the server was down.
Python (full semantics out‑of‑box), TypeScript, Go, Rust, and PHP. For languages other than Python, symbols are parsed but typed/call resolution is degraded until the respective toolchain is installed; this never blocks `init`.
Deep ripple effects from a rename may require a full `reindex`; incremental edits on cross‑language boundaries may become exact only after a `reindex`. The watcher re‑links only the connected set, not the entire project.
Its A/B benchmark (against `semble`, `codegraph`, and a no‑tools control) shows it achieves higher or comparable accuracy on hard impact questions while keeping token costs low and flat across strong and weak models, staying clearly ahead of the no‑tools control.


MCP server for managing Gologin browser profiles, proxies, fingerprints and cloud browser sessions through AI conversations

Hosted Google Search / SERP MCP server from HasData, no Google Cloud project. Organic results, AI Overview, People Also Ask, AI Mode, news and shopping for Claude, Cursor and any MCP client.

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab
Comments