Agentcairn vs Statelessagent — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agentcairn vs Statelessagent
In-depth architectural comparison of the Agentcairn and Statelessagent 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
Agentcairn
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Statelessagent
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Agentcairn if you need specialized Knowledge & Memory tools running via a local process. Choose Statelessagent 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 Agentcairn 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).
Primary tools included: Plain Markdown Obsidian vault as canonical memory store, Rebuildable DuckDB index for hybrid BM25, vector, and graph recall, Non-lossy memory capture with supersession and secret redaction.
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).
Primary tools included: Provenance tracking and stale knowledge detection, Dual-layer memory with atomic fact extraction, 19 MCP tools for session handoffs, decisions, and search.
Local-first agent memory: a plain-Markdown Obsidian vault is the source of truth, with a rebuildable DuckDB index for hybrid BM25 + vector + graph recall. Non-lossy capture with secret redaction; works across Claude Code, Codex, Cursor, and any MCP host. uvx agentcairn
Memory with provenance tracking — records where agent knowledge originated and detects when sources change. 17 MCP tools for session handoffs, decisions, semantic search, and knowledge graph. Works across Claude Code, Cursor, Windsurf, Codex CLI, and Gemini CLI. Single Go binary, SQLite + vector search, fully local.
Category & Scope
Tools & Capabilities Breakdown
Agentcairn Tools (6)
Plain Markdown Obsidian vault as canonical memory store
Rebuildable DuckDB index for hybrid BM25, vector, and graph recall
Non-lossy memory capture with supersession and secret redaction
Cross-agent shared vault for consistent context
Memory provenance, currency, and importance metadata
Integration with Claude Code, Codex, Cursor, and MCP hosts
Statelessagent 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).
Agentcairn is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Statelessagent belongs to Knowledge & Memory using local stdio subprocess. Select Agentcairn when you need capabilities focused on knowledge & memory and Statelessagent when you require tools for knowledge & memory.