In-depth architectural comparison of the Memxus Remote Mcp and Moxie Docs 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
Memxus Remote Mcp
Knowledge & Memory · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Memxus Remote Mcp if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Moxie Docs 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 Memxus Remote Mcp when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Shared context engine for devs and teams. Syncs GitHub, Notion, and saved decisions into reusable project context, so Claude, ChatGPT, Cursor, VS Code and Gemini start each session with the architecture and decisions the team already made. OAuth 2.1 PKCE, AES-256 encrypted, RFC 9728 compliant. https://mcp.memxus.com/mcp
MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Tools & Capabilities Breakdown
Memxus Remote Mcp Tools (13)
remember
Save context — manual input, decisions, or notes; optional `project:<slug>` collection
recall
Semantic search across memories; GitHub/Notion synced content via `project:<slug>` or tags
get_context
Formatted context block from GitHub, Notion, and saved decisions for agent prompts
list_memories
Browse memories by collection, tags, type, or visibility
get_memory
Retrieve full content and metadata by memory ID
list_collections
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).
Memxus Remote Mcp is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Memxus Remote Mcp when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.
List scopes; GitHub/Notion syncs appear under `project:<slug>
forget
Delete a memory permanently
memory_stats
Stats by type and collection
update
Patch or append existing memory content, tags, or type
connect_source
Start GitHub App install or Notion OAuth from chat
list_syncable_items
List repos or Notion pages available after connecting
set_sync_selection
Choose what to sync and trigger initial sync into `project:<slug>
+1 more tools listed on main page
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
Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
moxie.search_docs
Semantic + keyword search over generated docs, conventions, gaps, and AI context.
moxie.get_doc_gaps
Unresolved documentation gaps with severity and the paths they concern.
moxie.get_documentation_opportunities
Recommended doc work: missing docs, drift repairs, and PR templates.
moxie.get_documentation_patterns
How the repository organizes and maintains its docs (where new docs belong).
moxie.list_docs
Paginated, section-grouped table of contents of every generated doc.
moxie.propose_doc_update
Add or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
moxie.propose_doc_removal
Remove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.