ripwireRed Hat's 'ripgrep of AI context': a zero-dependency C++23 CLI + MCP that hands a coding agent a ranked call graph — what to touch, blast radius, tests to run — with no index server.
Why switchSame shape — one static binary, tree-sitter graph, compiler-grade resolution, many languages — ripwire differentiates on change-oriented ranking (`--for`), published evals against graph-DB MCPs, and an explicit lineage of the metrics it uses.
Full comparison → codebase-memory-mcpCode intelligence MCP in pure C: tree-sitter knowledge graph over 158 languages, average repo indexed in milliseconds, sub-ms queries, 10x fewer tokens. Single static binary, zero deps.
Why switchThe closest fight on the shelf: both are single-binary tree-sitter knowledge graphs served over MCP. codebase-memory-mcp bets on C-core minimalism; gortex on language breadth and cross-service resolution.
Full comparison → serenaThe IDE for your coding agent: an MCP toolkit giving symbol-level retrieval, editing, refactoring and debugging over real language servers — or a JetBrains plugin backend.
Why switchBoth give agents symbol-level code intelligence over MCP. Gortex ships one static Go binary with a tree-sitter graph across 257 languages and compiler-grade resolution for 17; Serena leans on real language servers, so its depth follows the LSP ecosystem rather than its own parsers.
Full comparison → tokensaveCode-intelligence MCP server for coding agents — a pre-indexed semantic graph (libSQL + FTS5) they query instead of grepping: symbols, callers, impact radius in one call. 100% local, 50+ languages.
Why switchSame pitch — a pre-indexed semantic graph agents query instead of grepping. tokensave is the lean libSQL take; gortex scales the same idea to multi-repo and 257 languages.
Full comparison → code-graph-ragParses a polyglot monorepo with Tree-sitter into a Memgraph knowledge graph: query it in plain English (NL→Cypher), trace data flow, find dead code, edit via AST-surgical patches.
Why switchBoth build a tree-sitter graph of a polyglot repo; code-graph-rag stands up Memgraph and answers plain-English queries, gortex ships one static Go binary exposing MCP tools. Query surface vs zero infrastructure.
Full comparison → codegraph-mcpNo-train, on-prem code knowledge graph served to AI agents over MCP — symbols, call edges, cross-language links and blast-radius queries, with a hash-chained audit log of every read.
Why switchBoth serve on-prem code graphs with call edges and cross-language links over MCP; codegraph-mcp differentiates on the hash-chained audit log, gortex on coverage and agent integrations.
Full comparison →