Codebase Memory vs State Memory MCP
Two MCP servers from our memory ranking, compared on live data - updated nightly, never sponsored.
Bottom line · 2026-09-18
Codebase Memory records more monthly package installs (43,666 vs 21,257); both are actively maintained, with commits inside the last month.
How they differ in kind
Codebase Memory focuses on: The fastest and most efficient code intelligence engine for AI coding agents. State Memory MCP focuses on: @putervision/state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with a… Implementation languages differ (C vs TypeScript).
What each one does
Codebase Memory
The fastest and most efficient code intelligence engine for AI coding agents. Full-indexes an average repository in milliseconds, the Linux kernel (28M LOC, 75K files) in 3 minutes. Answers structural queries in under 1ms. Ships as a native executable with a small verified runtime-asset set for macOS, Linux, and Windows - download, run install, done.
From the project's README.
State Memory MCP
@putervision/state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server that provides AI coding assistants (such as Cursor, Claude Code, Gemini, or Copilot) with a structured, persistent SQLite graph for tracking workflow state - tasks, decisions, artifacts, plans, blockers, and their semantic relationships. It runs locally over stdio via the published package.
From the project's README.
14 signals, side by side
| Signal | Codebase Memory | State Memory MCP |
|---|---|---|
| Monthly installs | 43,666 | 21,257 |
| GitHub stars | 43,715 | 89 |
| Last commit | 2026-09-18 | 2026-09-15 |
| Releases · last 90 days | 9 | 2 |
| In the registry since | Feb 2026 | Jul 2026 |
| Registry versions | 14 | 10 |
| Documented tools | not extracted - see README | not extracted - see README |
| Env vars extracted | none extracted - see README | none extracted - see README |
| Runs | local (stdio) | local (stdio) |
| Endpoint auth | local only | local only |
| Maintenance | actively maintained | actively maintained |
| License | MIT | MIT |
| Language | C | TypeScript |
| Category rank | #1 of 304 | #4 of 304 |
Which one, for what
Derived from the signals above, not hands-on testing.
Pick Codebase Memory if…
- → release velocity matters - 9 releases in 90 days vs 2
- → you prefer a C codebase to extend or audit
Pick State Memory MCP if…
- → you prefer a TypeScript codebase to extend or audit
- → category standing - #4 of 304 maintained memory servers
Who's behind them
Codebase Memory - deusdata: 1 MCP server tracked, 1 maintained, 43,715 combined stars.
State Memory MCP - putervision: 6 MCP servers tracked, 6 maintained, 210 combined stars. Full record.
Not sold on either?
The next-ranked memory servers we track:
Quick answers
Is Codebase Memory better than State Memory MCP?
Package installs favor Codebase Memory: 43,666 monthly installs to 21,257. State Memory MCP still ranks #4 of 304 maintained memory servers. Data as of 2026-09-18; we haven't hands-on tested either.
Can I use Codebase Memory and State Memory MCP together?
Yes - MCP clients accept multiple servers in one config, so you can enable both memory servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.
Keep exploring: best memory servers · TypeScript servers · all comparisons · every server
Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-09-18.