Side-by-Side Model Context Protocol Comparison
Moxie Docs MCP vs Session Watcher
In-depth architectural comparison of the Moxie Docs MCP and Session Watcher 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
Developer Tools · Local stdio
Quality: 72/100 (Great) | Auth: API Key required
Session Watcher
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Moxie Docs MCP if you need specialized Developer Tools tools running via a local process. Choose Session Watcher if your workspace requires Developer Tools 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 Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Freemium).
- You have access to required keys:
MOXIE_TOKEN. - Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Choose Session Watcher when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: start_watcher, stop_watcher, watcher_status.
Feature & Specification Comparison
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
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.
Session Watcher Tools (7)
start_watcher
Start (or reuse) the dashboard server; returns its URL
stop_watcher
Stop the managed server
watcher_status
Report whether the server is running and its URL
rotate_session
Rotate to a new session ID
get_bucket_summary
Return current context bucket structure (files, skills, tools) with metrics
prepare_handoff
Persist selected paths + summary as a handoff package; returns a semantic token
load_handoff
Load a handoff by token, free-text search, or auto-match for the current project
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 Configuration
Session Watcher Configuration