In-depth architectural comparison of the Obsidian MCP Pro 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
Obsidian MCP Pro
Knowledge & Memory · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Obsidian MCP Pro if you need specialized Knowledge & Memory tools running via a local process. 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 Obsidian MCP Pro 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: MCP_PORT, MCP_VAULT_PATH, MCP_TRUSTED_ORIGINS, MCP_LOG_LEVEL.
Feature-complete Obsidian vault MCP server with 23 tools and 3 resources. Full-text search, note CRUD, frontmatter queries, tag management, backlinks, graph traversal (BFS up to 5 hops), orphan/broken link detection, and canvas support. Auto-detects vault, path traversal protection, MIT licensed.
MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Tools & Capabilities Breakdown
Obsidian MCP Pro Tools (41)
search_notes
Focus-ranked full-text search with query-centered snippets (cached)
get_note
Read a note whole, or by `section` / `block` / `lines
list_notes
List notes in the vault or a folder
get_daily_note
Get today's (or a specific date's) daily note
search_by_frontmatter
Find notes by frontmatter property values with case-insensitive key/value matching
get_recent_notes
Notes sorted by mtime; optional ISO-or-relative `since` filter
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).
Obsidian MCP Pro is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Obsidian MCP Pro when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.
Vault counts, bytes, words, tag coverage, most-recent note
resolve_alias
Translate frontmatter alias (or basename) to note path
create_note
Create a new note with content and frontmatter
append_to_note
Append content to an existing note
prepend_to_note
Prepend content after frontmatter
update_frontmatter
Update frontmatter properties on a note
+29 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.