Dependency graph + 23 MCP tools for AI coding assistants. Impact analysis, health scoring, security scanner, agent coordination.
If you already use Depwire, the depwire mcp server is the piece that lets your assistant work with it directly. Dependency graph + 23 MCP tools for AI coding assistants. Impact analysis, health scoring, security scanner, agent coordination.
Depwire builds a DETERMINISTIC, NOT PROBABILISTIC dependency graph of your codebase. This is not RAG. There are no embeddings, no similarity scores, no vector databases, no guesses. Depwire uses tree-sitter — the same parser powering GitHub's code intelligence — to extract exact symbol-level facts from every file: every function, every class, every interface, every import and export relationship, across 17 programming languages. When you ask "what breaks if I delete encodeToken in auth/token.ts?", Depwire does not search for similar-looking code and estimate an answer. It traverses the exact dependency
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
connect_repo — Connect to any local project or GitHub repoget_architecture_summary — High-level project overviewget_file_context — Full context — imports, exports, dependents. Includes cross-language connectionsget_dependencies — What does a symbol depend on?get_dependents — What depends on this symbol?get_symbol_info — Look up any symbol's detailssearch_symbols — Find symbols by name across the codebaselist_files — List all files with statsimpact_analysis — What breaks if you change a symbol? Cross-language edges includedvisualize_graph — Generate interactive arc diagramget_health_score — 0-100 health score with recommendationsfind_dead_code — Symbols defined but never referencedInstallation goes through your MCP client rather than a global install: point it at depwire-cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Depwire's toolset — connect_repo, get_architecture_summary, get_file_context and 11 more — is a fair guide to whether it matches your workflow. It is maintained by depwire; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| connect_repo | Connect to any local project or GitHub repo |
| get_architecture_summary | High-level project overview |
| get_file_context | Full context — imports, exports, dependents. Includes cross-language connections. |
| get_dependencies | What does a symbol depend on? |
| get_dependents | What depends on this symbol? |
| get_symbol_info | Look up any symbol's details |
| search_symbols | Find symbols by name across the codebase |
| list_files | List all files with stats |
| impact_analysis | What breaks if you change a symbol? Cross-language edges included. |
| visualize_graph | Generate interactive arc diagram |
| get_health_score | 0-100 health score with recommendations |
| find_dead_code | Symbols defined but never referenced |
| get_project_docs | Retrieve auto-generated codebase documentation |
| update_project_docs | Regenerate documentation on demand |
{
"mcpServers": {
"depwire": {
"command": "npx",
"args": ["-y", "depwire-cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.