Plur vs State Memory MCP

Two MCP servers from our memory ranking, compared on live data - updated nightly, never sponsored.

Bottom line · 2026-09-18

State Memory MCP records more monthly package installs (21,257 vs 7,596); both are actively maintained, with commits inside the last month.

How they differ in kind

Plur focuses on: Persistent, open memory for AI agents - local-first, zero-cost, shared across MCP tools (Claude Code, Codex, Cursor, Hermes, OpenClaw). 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…

What each one does

Plur

Persistent, open memory for AI agents - local-first, zero-cost, shared across MCP tools (Claude Code, Codex, Cursor, Hermes, OpenClaw). Your agent's memory is plain-text engrams you can read, correct, and delete - not weights you can't. Its 15 documented tools cover plur, learn.

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 Plur State Memory MCP
Monthly installs 7,596 21,257
GitHub stars 291 89
Last commit 2026-09-18 2026-09-15
Releases · last 90 days 10+ 2
In the registry since Jul 2026 Jul 2026
Registry versions 14 10
Documented tools 15 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 Apache-2.0 MIT
Language TypeScript TypeScript
Category rank #5 of 304 #4 of 304

What their tools cover

Extracted from each project's README - the tools each server hands your agent. A missing list means the README doesn't document one, not that no tools exist.

Plur 15 tools documented

  • plur_learn - Store a correction, preference, or convention
  • plur_learn_batch - Store many engrams in one call (batch dedup + per-item failure…
  • plur_recall - Retrieve relevant memories - hybrid (BM25 + embeddings) by default…
  • plur_inject_hybrid - Select engrams for current task within token budget
  • plur_feedback - Rate relevance (trains quality over time)
  • plur_forget - Retire a memory (activation decays, eventually pruned)
  • plur_rescope - Move an existing engram to another scope - personal → team, or back
  • plur_session_scope - Change the session's default write scope mid-session

+7 more on the full page

State Memory MCP no tool list in README

Which one, for what

Derived from the signals above, not hands-on testing.

Pick Plur if…

  • → release velocity matters - 10+ releases in 90 days vs 2
  • → its documented toolset fits - 15 tools including plur_learn, plur_learn_batch

Pick State Memory MCP if…

  • → measured package adoption matters - 21,257 monthly installs
  • → category standing - #4 of 304 maintained memory servers

Who's behind them

Plur - plur-ai: 1 MCP server tracked, 1 maintained, 291 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 Plur better than State Memory MCP?

Package installs favor State Memory MCP: 21,257 monthly installs to 7,596. Plur still ranks #5 of 304 maintained memory servers. Data as of 2026-09-18; we haven't hands-on tested either.

Can I use Plur 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.