Side-by-Side Model Context Protocol Comparison
Saihm MCP vs Being
In-depth architectural comparison of the Saihm 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.
At a Glance & Executive Verdict
Saihm MCP
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Being
Knowledge & Memory · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Saihm MCP 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 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. - Primary tools included: saihm_remember, saihm_recall, saihm_forget.
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
Tools & Capabilities Breakdown
Saihm MCP Tools (8)
saihm_remember
Store information in SAIHM persistent encrypted memory. Use this when a fact, decision, or piece of context should outlive the current session. Returns the cell id that saihm_forget takes.
saihm_recall
Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, and this client holds no keys. Use at the start of a session, or whenever past context is needed. Pass a keyword to filter, or leave empty to load all.
saihm_forget
Cryptographically erase one memory by its cell id (GDPR Art. 17). Destroying the key makes the content unreadable to everyone, the operator included. Irreversible: use it when erasure is the intent, not to tidy a working set.
saihm_status
Show the current SAIHM session: agent identity, tier, the prs and bfsi scores, storage by tier, and sharing state, as far as the operator reports them — a non-custodial operator cannot see stored-byte totals. Use it to check the agent identity, custody mode, and what the operator reports about storage and sharing.
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).
Saihm MCP Configuration
Being Configuration