Codebase Memory Mcp vs Tarn

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
C
💻 Developer Tools
T
Tarn
NazarKalytiuk
💻 Developer Tools
SummaryCode-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcpCLI-first API testing tool with structured JSON failures (failurecategory, errorcode, hints) so AI agents can branch on the taxonomy without parsing stderr. MCP tools: tarnrun, tarnvalidate, tarnfixplan, tarninspect, tarnrerunfailed, and more. Tests are .tarn.yaml. Single static binary (musl), MIT.
Quality signal33/100 (Emerging)23/100 (Emerging)
Install pathnpx · highnpx · low
Engagement 1 0 0 37,079 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Codebase Memory McpView Tarn
More alternatives to Codebase Memory McpMore alternatives to TarnDeveloper Tools category

Other servers like Codebase Memory Mcp