What is the key difference between Mnemos and Being?

Mnemos belongs to the Knowledge & Memory category with local stdio execution, while Being belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Mnemos or Being 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 Mnemos and Being free or paid?

Mnemos operates under a Free / Open Source model (No auth required). Being operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Mnemos lists 9 tools with 2 views and 22 GitHub stars. Being lists 6 tools with 2 views and 1 GitHub stars.

Can I use both Mnemos and Being 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

Mnemos vs Being

In-depth architectural comparison of the Mnemos and Being 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

Mnemos

Knowledge & Memory · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Being

Knowledge & Memory · Remote HTTP/SSE

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

Verdict Summary: Choose Mnemos if you need specialized Knowledge & Memory tools running via a local process. Choose Being if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mnemos when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: mnemos_store, mnemos_search, mnemos_context.

Explore Mnemos Details

Choose Being when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, ENCRYPTION_KEY.
Primary tools included: Structured SOUL personality definitions, Scene-based episodic memory with decay and consolidation, Patrol background reflection and memory processing.

Feature & Specification Comparison

Specification	Mnemos s60yucca Knowledge & Memory	Being wnbhr Knowledge & Memory
Summary	Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across sessions. Single Go binary with embedded SQLite, FTS5 search, context assembly within token budgets, and autopilot setup for Claude Code, Kiro, and Cursor.	Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.
Category & Scope

Tools & Capabilities Breakdown

Mnemos Tools (9)

mnemos_store

Store a memory (full auto-pipeline runs transparently)

mnemos_search

Hybrid FTS + semantic + file-overlap search

mnemos_context

Assemble budget-aware, MMR-diversified context

mnemos_get

Fetch by ID

mnemos_update

Update content, summary, or tags

mnemos_delete

Soft-delete (recoverable via maintain)

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).

Mnemos Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "s60yucca-mnemos": {
      "command": "npx",
      "args": [
        "-y",
        "@s60yucca/mnemos"
      ]
    }
  }
}

Being Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wnbhr-being": {
      "url": "https://being.ruddia.com/mcp/"
    }
  }
}

Frequently Asked Questions

Mnemos is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Being belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Mnemos when you need capabilities focused on knowledge & memory and Being when you require tools for knowledge & memory.

More alternatives to Mnemos More alternatives to Being Knowledge & Memory category hub