In-depth architectural comparison of the Moxie Docs MCP 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
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Statelessagent
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Moxie Docs MCP 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 Moxie Docs 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 (Freemium).
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.
MCP & Agent Skills for Automated Documentation, and codebase conventions + context
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.
Tools & Capabilities Breakdown
Moxie Docs MCP Tools (12)
moxie.get_ai_context
Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
moxie.get_doc_impact
Given the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.
moxie.get_api_context
Given paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.
moxie.review_change
Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.
moxie.get_conventions
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).
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Statelessagent belongs to Knowledge & Memory using local stdio subprocess. Select Moxie Docs MCP when you need capabilities focused on knowledge & memory and Statelessagent when you require tools for knowledge & memory.