Moxie Docs MCP vs Being

In-depth architectural comparison of the Moxie Docs MCP 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.

Which MCP Server Should You Choose?

Choose Moxie Docs 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 (Freemium).
• Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP 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	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory	Being wnbhr Knowledge & Memory
Summary	MCP & Agent Skills for Automated Documentation, and codebase conventions + context	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

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

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

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

Related MCP Server Comparisons