Semantic code graph MCP server for coding agents
Connect Graphlens to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Semantic code graph MCP server for coding agents. The graphlens mcp server is what makes that connection.
A free, MIT-licensed MCP server that gives coding agents (Claude Code, Cursor, and compatible clients) a semantic code graph of your project — symbols, cross-file calls, references, imports and cross-language boundaries.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
search — Find code by NAME, CONTENT, or MEANING — the one way in. Returns graph nodes with their signature (often enough to answer without a follow-uprelations — A symbol's neighbourhood in one call: callers, callees, implementors/subclasses, and non-call references — each with its signature. Theinfo — Read a specific target: a symbol (node id or name) → source + signature + location; a file path → its symbol outlineInstallation goes through your MCP client rather than a global install: point it at graphlens-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Graphlens's toolset — search, relations, info — is a fair guide to whether it matches your workflow. It is maintained by Neko1313; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Graphlens's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| search | Find code by NAME, CONTENT, or MEANING — **the one way in**. Returns graph nodes with their signature (often enough to answer without a follow-up call). Content is matched literally, not as a regex. Scope with path_glob |
| relations | A symbol's neighbourhood in one call: callers, callees, implementors/subclasses, and non-call references — each with its signature. **The** impact-analysis tool ("what breaks if I change X?", "what implements X?") |
| info | Read a specific target: a symbol (node id or name) → source + signature + location; a file path → its symbol outline |
{
"mcpServers": {
"graphlens": {
"command": "uvx",
"args": ["graphlens-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.