A2cr vs Basemouse Core — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
A2cr vs Basemouse Core
In-depth architectural comparison of the A2cr and Basemouse Core 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
A2cr
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Basemouse Core
Knowledge & Memory · Remote HTTP/SSE
Quality: 43/100 (Fair) | Auth: API Key required
Verdict Summary: Choose A2cr if you need specialized Knowledge & Memory tools running via a local process. Choose Basemouse Core 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 A2cr when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: A2CR_LOCAL_DB, A2CR_UI_URL.
Primary tools included: Stores WorkBaton, WorkStash, WorkThread, actor, and event records locally, Client-encrypted checkpoint and note storage, SQLite database backend with no cloud or account needed.
MCP server for AI-agent handoffs. Saves client-encrypted WorkBaton checkpoints and WorkStash notes so Codex, Claude Code, Roo Code, and other MCP clients can resume work without passing full chat history.
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
Category & Scope
Tools & Capabilities Breakdown
A2cr Tools (6)
Stores WorkBaton, WorkStash, WorkThread, actor, and event records locally
Client-encrypted checkpoint and note storage
SQLite database backend with no cloud or account needed
Supports multiple MCP clients including Codex, Claude Code, and Cursor
Local browser dashboard with token-protected access
Compatibility with Python stdio wrapper and Node MCPB for Claude Desktop
Basemouse Core 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).
A2cr is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Basemouse Core belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select A2cr when you need capabilities focused on knowledge & memory and Basemouse Core when you require tools for knowledge & memory.
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.