Skip to content
AI Tool

state-memory-mcp Review

state-memory-mcp is a zero-infrastructure, deterministic Model Context Protocol (MCP) server for developer AI agents, providing persistent long-term state memory.

shipped Sep 16, 2026freemium
state-memory-mcp — product screenshot

Why it matters

1Offers a free tier for initial access.
2Utilizes local SQLite storage for persistent long-term state memory.
3Employs relationship-aware symbol graph traversals for deterministic data retrieval.
4Supports Spec-Driven Development contracts with real-time drift detection.

About state-memory-mcp

Business Model
Open Source
Usage Pricing
$15.00 / M tokens, $10.00 / M tokens, $3.00 / M tokens, $2.50 / M tokens, $2.00 / M tokens, $1.10 / M tokens, $0.55 / M tokens, $0.14 / M tokens, $0.075 / M tokens per tokens
Funding
open-source
Target Audience
Developers and AI practitioners

Cost Examples

  • • Estimated API Cost Saved: $0.480
API DocsGitHubOpen Source

Specs

API Available

Yes, public API

Screenshots

overview

What is state-memory-mcp?

state-memory-mcp is a Model Context Protocol (MCP) server tool developed by PuterVision that enables developer AI agents to track workflow state, decisions, and blockers. It provides persistent long-term state memory for AI agents, managing task execution DAGs, architectural decision logs, and session context.

features

Key Features of state-memory-mcp

state-memory-mcp provides a suite of features designed to enhance the performance and reliability of AI agents by offering structured, persistent memory and deterministic operations. These capabilities aim to reduce context bloat and improve the efficiency of multi-turn AI interactions.

  • Persistent long-term state memory for AI agents.
  • Deterministic operations via relationship-aware symbol graph traversals.
  • 3D graph visualizer for understanding workflow state.
  • Cryptographic session auditing using SHA-256 for tamper-evident audit trails.
  • Spec-driven development contract management with real-time drift detection.
  • Management of task execution Directed Acyclic Graphs (DAGs).
  • Maintenance of architectural decision logs.
  • Tracking of artifact outputs, milestones, and active blockers.
  • Local SQLite storage (.state-memory-mcp/graph.db) for externalizing workflow state.
  • Support for a 'Multi-Agent Blackboard' as a Shared Context Store (SCS).

use cases

Who Should Use state-memory-mcp?

state-memory-mcp is primarily designed for developer AI agents and the developers who build and deploy them. Its capabilities are particularly beneficial in scenarios requiring consistent state tracking, decision logging, and efficient context management across complex development workflows.

  • Developer AI agents (e.g., Cursor, Gemini, Claude Code, Windsurf) requiring persistent long-term state memory.
  • Teams managing complex task execution DAGs in software development.
  • Architects and developers needing to maintain auditable architectural decision logs.
  • Projects focused on Spec-Driven Development, requiring real-time contract drift detection from Markdown PRDs, OpenSpec, and Gherkin BDD .feature files.
  • Environments where reducing LLM context bloat and prompt overhead is critical for cost and performance optimization.

how to use

How to Use state-memory-mcp

state-memory-mcp functions as a local, structured memory server for AI coding assistants. It integrates via the Model Context Protocol (MCP) to manage and store various aspects of a development workflow.

  • 1Install the state-memory-mcp server locally.
  • 2Configure AI agents to communicate with the MCP server via its API.
  • 3Utilize the server to store and retrieve task execution DAGs.
  • 4Log architectural decisions and their rationale within the graph.
  • 5Track artifact outputs, milestones, and active blockers for ongoing projects.
  • 6Ingest and manage Spec-Driven Development contracts for drift detection.

pricing

state-memory-mcp Pricing & Plans

state-memory-mcp operates on a freemium and open-source business model, offering usage-based pricing for its services. The cost is calculated per million tokens processed, with various tiers available.

  • Usage Pricing: $15.00 / M tokens
  • Usage Pricing: $10.00 / M tokens
  • Usage Pricing: $3.00 / M tokens
  • Usage Pricing: $2.50 / M tokens
  • Usage Pricing: $2.00 / M tokens
  • Usage Pricing: $1.10 / M tokens
  • Usage Pricing: $0.55 / M tokens
  • Usage Pricing: $0.14 / M tokens
  • Usage Pricing: $0.075 / M tokens

Enjoying this? Get one like it in your inbox each morning.

one email a day · unsubscribe in two clicks · no third-party tracking

Pros

  • +Provides deterministic state memory, reducing AI agent hallucination loops.
  • +Reduces LLM context bloat and prompt overhead by externalizing state to local SQLite.
  • +Offers cryptographic session auditing with SHA-256 for tamper-evident audit trails.
  • +Supports Spec-Driven Development with real-time drift detection for contracts.
  • +Functions as a 'Multi-Agent Blackboard' for parallel subagent communication.
  • +Open-source core with a freemium usage-based pricing model.

Cons

  • −Specific recent updates for state-memory-mcp itself are not prominently detailed beyond its initial description.
  • −Some users express skepticism about memory MCPs potentially saving irrelevant memories or LLM hallucinations.
  • −Potential for limited enterprise adoption without explicit support for serverless runtimes.
  • −Requires integration with AI agents via the Model Context Protocol (MCP), which may involve initial setup.
  • −Pricing is usage-based per token, which can vary with agent activity.

Similar Tools

state-memory-mcp vs Competitors

state-memory-mcp differentiates itself from other memory solutions and graph databases by offering a specialized, zero-infrastructure, deterministic Model Context Protocol (MCP) server focused on AI agent state management. It contrasts with general-purpose graph databases and probabilistic vector search systems.

1

A mature, dedicated graph database designed for highly connected data, offering powerful query capabilities with Cypher.

Neo4j is a general-purpose graph database, requiring more setup and explicit schema design for workflow state compared to state-memory-mcp's specialized focus. It offers greater flexibility and scalability for complex graph data but might have a steeper learning curve for simple state tracking.

2

A multi-model database supporting graph, document, and key-value data, allowing for flexible data modeling beyond just graphs.

ArangoDB provides a multi-model approach, which can be more versatile if your state tracking needs extend beyond pure graph structures, but it might require more configuration to specifically replicate state-memory-mcp's deterministic graph server behavior. It offers broader database capabilities at the cost of specialized focus.

3
Dgraph↗

A distributed, open-source graph database designed for scale and real-time queries, using GraphQL as its query language.

Dgraph is built for distributed environments and offers GraphQL API access, which can be advantageous for scalable AI workflows. However, it might have a steeper operational overhead for smaller, single-instance deployments compared to state-memory-mcp's potentially simpler server model.

More on Stork

Related AI Tools

Other tools in this category, matched by shared tags

One short daily email of tools worth shipping. No drip funnel.

one email a day · unsubscribe in two clicks · no third-party tracking

For builders

This page is doing a job for someone else’s tool.

AI agents read it. Buyers land on it. It answers in eight languages and over MCP. Your tool can have one like it — live in 24 hours.