In-depth architectural comparison of the Central Intelligence and Obsidian 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
Central Intelligence
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Obsidian MCP
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Central Intelligence if you need specialized Knowledge & Memory tools running via a local process. Choose Obsidian 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 Central Intelligence 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).
You have access to required keys: CI_API_KEY.
Primary tools included: Five MCP tools: remember, recall, context, forget, share, Semantic search via vector embeddings, Agent, user, and organization scoped memory.
Persistent memory for AI agents. Five tools (remember, recall, context, forget, share) with semantic search via vector embeddings and agent/user/org scoping. Works with Claude Code, Cursor, Windsurf, and any MCP client.
Self-hosted MCP server for Obsidian with semantic + full-text search over PostgreSQL/pgvector, wikilink graph traversal, atomic note CRUD, OAuth 2.0, and a self-describing vault guide.
Category & Scope
Tools & Capabilities Breakdown
Central Intelligence Tools (6)
Five MCP tools: remember, recall, context, forget, share
Semantic search via vector embeddings
Agent, user, and organization scoped memory
Verbatim memory retrieval without rewriting
Cross-tool memory integration with AI coding platforms
Open-source with Apache 2.0 license
Obsidian MCP Tools (6)
Semantic and full-text search via PostgreSQL with pgvector
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).
Central Intelligence is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Obsidian MCP belongs to Knowledge & Memory using local stdio subprocess. Select Central Intelligence when you need capabilities focused on knowledge & memory and Obsidian MCP when you require tools for knowledge & memory.
Primary tools included: Semantic and full-text search via PostgreSQL with pgvector, Atomic CRUD operations on markdown notes, Wikilink graph traversal for contextual navigation.