GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Indexes codebase into a local knowledge graph with 40+ AI tools and codebase-guard.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"codebase-synapse": {
"command": "npx",
"args": [
"-y",
"codebase-synapse"
]
}
}
}Run this in your terminal
claude mcp add codebase-synapse -- npx -y codebase-synapsePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"codebase-synapse": {
"command": "npx",
"args": [
"-y",
"codebase-synapse"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"codebase-synapse": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"codebase-synapse"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account iwiels, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.13) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Give your AI agent a deep understanding of your entire codebase.
An MCP server that indexes your codebase into a local knowledge graph with 52 AI tools — semantic search, call-graph traversal, git archaeology, blast-radius analysis, and more.
Works with Claude Code · Cursor · Windsurf · Zed · Any MCP client
AI coding agents (Claude, Cursor, etc.) are powerful — but they work with limited context. They can only see the files you open or feed them. Ask about call chains, architectural patterns, or blast-radius impact, and they guess.
Codebase Synapse fixes this. It indexes your entire repo into a local knowledge graph stored in SQLite, giving your AI agent real answers backed by structural analysis — not hallucinations.
graph LR
A["📁 Your Codebase"] -->|Tree-sitter| B["🧩 Parser"] B -->|Symbols & Edges| C["🕸️ Knowledge Graph"] C -->|SQLite| D["💾 Local DB"] D -->|52 MCP Tools| E["🤖 AI Agent"]
style A fill:#1a1b26,stroke:#7aa2f7,color:#c0caf5 style B fill:#1a1b26,stroke:#bb9af7,color:#c0caf5 style C fill:#1a1b26,stroke:#9ece6a,color:#c0caf5 style D fill:#1a1b26,stroke:#e0af68,color:#c0caf5 style E fill:#1a1b26,stroke:#f7768e,color:#c0caf5
codebase-synapse index /path/to/your/repo
Indexing runs as a separate CLI command and writes into ~/.codebase-synapse/codebase.db. The first index is the slow one; re-running it only re-indexes changed files. The MCP server never indexes — it only reads the pre-built index.
npx codebase-synapse
That's it. No Docker. No database setup. No cloud. The server starts via stdio and serves the pre-built index to your MCP client.
Claude Code / Claude Desktop
Add to your claude_desktop_config.json or mcp_servers.json:
{
"mcpServers": { "codebase-synapse": { "command": "npx", "args": ["-y", "codebase-synapse"] } } }
Cursor
Add to your .cursor/mcp.json:
{
"mcpServers": { "codebase-synapse": { "command": "npx", "args": ["-y", "codebase-synapse"] } } }
Other MCP clients
Any MCP client that supports stdio transport works. Just point it at:
npx -y codebase-synapse
| Tool | Description |
|---|---|
semantic_search | Vector similarity search using local embeddings (all-MiniLM-L6-v2) |
search_code | Full-text search across code (FTS5 + BM25 ranking) |
search_symbol | Find functions, classes, types by name or pattern |
hybrid_search | Combined semantic + lexical search with RRF fusion |
find_similar | Find structurally similar code using MinHash + LSH |
find_symbol_everywhere | Locate a symbol across all indexed projects |
| Tool | Description |
|---|---|
get_callers / get_callees | Navigate the call graph in either direction |
get_imports / get_dependents | Trace dependency chains |
impact_analysis | Compute blast radius before editing a file |
find_path | Find the shortest connection between two symbols |
find_dead_code | Detect unreachable functions and unused exports |
get_pagerank | Identify the most critical nodes in your architecture |
query_graph | Run Cypher-like queries against the knowledge graph |
| Tool | Description |
|---|---|
get_architecture | Full project architecture overview (languages, entry points, hotspots) |
get_file_structure | Directory tree with symbol annotations |
project_overview | High-level summary with key metrics |
get_route_map | Extract HTTP routes and their handler mappings |
suggest_boundaries | Detect module boundaries via Leiden clustering |
check_boundaries | Validate cross-module dependencies against defined boundaries |
get_clusters | Community detection across the codebase |
| Tool | Description |
|---|---|
git_archaeology | Deep history analysis of a file (authors, churn, evolution) |
get_hotspots | Files with highest complexity × change frequency |
detect_change_coupling | Files that always change together |
get_recent_semantic_changes | Semantically meaningful recent changes |
index_git_history | Build temporal analysis from git log |
| Tool | Description |
|---|---|
memory_store / memory_search / memory_list | Persistent notes, facts, and decisions across sessions |
session_remember / session_recall | Short-term memory within a session |
get_context | Budgeted context preparation for AI agents |
get_edit_context | Focused context for a specific file edit |
get_working_set | Recently accessed and modified files |
manage_adr | Architecture Decision Records management |
Included as a bonus: `codebase-guard` is a PreToolUse hook for Claude Code that blocks writes to high-impact files until the agent runs impact_analysis first.
It uses PageRank scores and blast-radius data from the knowledge graph to identify architectural hubs. No more accidental edits to core files.
| Language | Rust (compiled native binary) |
| Transport | MCP stdio (JSON-RPC) |
| Storage | SQLite (WAL mode, zero config) |
| Embeddings | all-MiniLM-L6-v2 via Candle (offline, local, lazy-loaded) |
| Parsing | Tree-sitter (10 languages) |
| Distribution | npm with prebuilt binaries (Windows, macOS, Linux × x64, arm64) |
Rust · Python · TypeScript · JavaScript · Go · Java · C# · PHP · C · C++
src/
├── parser/ # Tree-sitter parsing & entity extraction ├── graph/ # Knowledge graph, PageRank, Leiden clustering ├── indexer/ # Repository indexing pipeline ├── search/ # BM25 full-text + vector cosine + hybrid RRF ├── embedding/ # Candle-based local embeddings (feature-gated) ├── memory/ # Persistent & session memory stores ├── mcp/ # MCP protocol transport + 52 tool handlers ├── git/ # Git archaeology, intent classification, hotspots ├── context/ # Budgeted context preparation for AI ├── cypher/ # Nom-based Cypher parser → SQL CTE planner ├── similarity/ # MinHash + LSH structural similarity ├── semantic/ # Multi-signal scoring (tokens, directory, AST) └── cli/ # Interactive TUI installer + artifact export/import
Contributions are welcome! The project uses standard Rust tooling:
# Run tests
cargo test
cargo clippy -- -D warnings
cargo fmt --all
Apache-2.0