Basemouse Core vs Mcp Obsidian — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Basemouse Core vs Mcp Obsidian
In-depth architectural comparison of the Basemouse Core and Mcp Obsidian 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
Basemouse Core
Knowledge & Memory · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: API Key required
Mcp Obsidian
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Basemouse Core if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Mcp Obsidian 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 Basemouse Core 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 (Paid Service).
You have access to required keys: DATABASE_URL, DATABASE_CA_CERT, BASEMOUSE_VECTOR_RETRIEVAL, BASEMOUSE_API_KEY.
Primary tools included: Durable Postgres-backed or in-memory seed document store, Lexical and hybrid retrieval combining lexical, graph, and local vector signals, Agent-ready context pack exports with citations and provenance.
Shared, versioned memory for your agents across Claude Code, Cursor, Kiro and Grok. One MCP server, sourced answers, full history. Remote Streamable HTTP; anonymous browses a public demo corpus. Tools: search, getcontextpack, upsertdocument. https://basemouse.com/mcp
Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.
Category & Scope
Tools & Capabilities Breakdown
Basemouse Core Tools (6)
Durable Postgres-backed or in-memory seed document store
Lexical and hybrid retrieval combining lexical, graph, and local vector signals
Agent-ready context pack exports with citations and provenance
Faceted search filtering by type and tag
Graph-aware document relationships with links and related lists
Web UI and API endpoints for search, context packs, and document management
Mcp Obsidian Tools (6)
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).
Basemouse Core is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Mcp Obsidian belongs to Knowledge & Memory using local stdio subprocess. Select Basemouse Core when you need capabilities focused on knowledge & memory and Mcp Obsidian when you require tools for knowledge & memory.
Safe YAML frontmatter parsing and AST-aware updates, File operations: read, write, patch, delete, move notes/files, Partial reads: get note outlines and specific line ranges