What is the key difference between Being and Saihm MCP?

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

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

Being operates under a BYOK (Pay Provider Direct) model (API Key required). Saihm MCP operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Being lists 6 tools with 2 views and 1 GitHub stars. Saihm MCP lists 8 tools with 3 views and 1 GitHub stars.

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

Being vs Saihm MCP

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

Being

Knowledge & Memory · Remote HTTP/SSE

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

Saihm MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Being if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Saihm 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 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.

Explore Being Details

Choose Saihm 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 (Free / Open Source).
You have access to required keys: SAIHM_ENDPOINT_URL, SAIHM_AUTH_HEADER.

Feature & Specification Comparison

Specification	Being wnbhr Knowledge & Memory	Saihm MCP SAIHM-Admin Knowledge & Memory
Summary	Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.	Sovereign, encrypted, persistent memory for AI agents. Eight MCP tools — remember, recall, forget (GDPR Art. 17 erasure), share. Anchored on COTI V2 mainnet. Apache-2.0. Install: npx -y @saihm/mcp-server.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Being Tools (6)

Structured SOUL personality definitions

Scene-based episodic memory with decay and consolidation

Patrol background reflection and memory processing

Ed25519 identity keys and signature chains

MCP server and REST API access

Bring-your-own LLM API key support

Saihm MCP Tools (8)

saihm_remember

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

Being Configuration

mcpServers (Claude Desktop / Cursor)

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

Saihm MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "saihm-admin-saihm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@saihm/mcp-server"
      ],
      "env": {
        "SAIHM_ENDPOINT_URL": "YOUR_SAIHM_ENDPOINT_URL_HERE",
        "SAIHM_AUTH_HEADER": "YOUR_SAIHM_AUTH_HEADER_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Being More alternatives to Saihm MCP Knowledge & Memory category hub Canonical compare URL