What is the key difference between Celiums Memory and Memstate MCP?

Celiums Memory belongs to the Knowledge & Memory category with local stdio execution, while Memstate MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Celiums Memory or Memstate MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Celiums Memory and Memstate MCP free or paid?

Celiums Memory operates under a Free / Open Source model (API Key required). Memstate MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Celiums Memory lists 6 tools with 2 views and 23 GitHub stars. Memstate MCP lists 6 tools with 2 views and 8 GitHub stars.

Can I use both Celiums Memory and Memstate MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Celiums Memory vs Memstate MCP

In-depth architectural comparison of the Celiums Memory and Memstate MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Celiums Memory

Knowledge & Memory · Local stdio

Quality: 53/100 (Good) | Auth: API Key required

Memstate MCP

Knowledge & Memory · Local stdio

Quality: 49/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Celiums Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Memstate MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Celiums Memory when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SQLITE_PATH, DATABASE_URL, QDRANT_URL, VALKEY_URL, CELIUMS_API_KEY, PORT, CELIUMS_LLM_API_KEY, CELIUMS_LLM_BASE_URL.
Primary tools included: Persistent memory with hybrid retrieval, Hash-chained agent journal, Layered ethics evaluation.

Explore Celiums Memory Details

Choose Memstate MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: .

Feature & Specification Comparison

Specification	Celiums Memory celiums Knowledge & Memory	Memstate MCP memstate-ai Knowledge & Memory
Summary	Cognitive memory engine with 5,100+ knowledge modules, circadian rhythm awareness, and emotional state tracking (PAD model). Hybrid search (PostgreSQL + Qdrant vectors + Valkey cache), per-user memory isolation, and multi-protocol support (MCP, REST, OpenAI, LangChain, A2A). npx @celiums/memory Website	Versioned, structured memory for AI agents. Stores facts as keypaths with full version history, automatic conflict detection, and O(1) token retrieval.
Category & Scope

Tools & Capabilities Breakdown

Celiums Memory Tools (6)

Persistent memory with hybrid retrieval

Hash-chained agent journal

Layered ethics evaluation

Circadian and affective state modulation

SQLite or PostgreSQL, Qdrant, and Valkey storage

61 typed MCP tools

Memstate MCP Tools (6)

Hierarchical keypath-based memory

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Celiums Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "celiums-celiums-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@celiums/memory"
      ],
      "env": {
        "SQLITE_PATH": "YOUR_SQLITE_PATH_HERE",
        "DATABASE_URL": "YOUR_DATABASE_URL_HERE",
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE",
        "VALKEY_URL": "YOUR_VALKEY_URL_HERE",
        "CELIUMS_API_KEY": "YOUR_CELIUMS_API_KEY_HERE",
        "PORT": "YOUR_PORT_HERE",
        "CELIUMS_LLM_API_KEY": "YOUR_CELIUMS_LLM_API_KEY_HERE",
        "CELIUMS_LLM_BASE_URL": "YOUR_CELIUMS_LLM_BASE_URL_HERE"
      }
    }
  }
}

Memstate MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memstate-ai-memstate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@memstate/mcp"
      ],
      "env": {
        "MEMSTATE_API_KEY": "YOUR_MEMSTATE_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Celiums Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memstate MCP belongs to Knowledge & Memory using local stdio subprocess. Select Celiums Memory when you need capabilities focused on knowledge & memory and Memstate MCP when you require tools for knowledge & memory.

More alternatives to Celiums Memory More alternatives to Memstate MCP Knowledge & Memory category hub