In-depth architectural comparison of the Easy Obsidian 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
Easy Obsidian Mcp
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Moxie Docs MCP
Knowledge & Memory · Local stdio
Quality: 82/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Easy Obsidian Mcp 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 Easy Obsidian 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 (Free / Open Source).
You have access to required keys: OBSIDIAN_API_KEY.
Interact with Obsidian vaults for knowledge management. Create, read, update, and search notes. Works with local Obsidian vaults using filesystem access.
MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope
Tools & Capabilities Breakdown
Easy Obsidian Mcp Tools (6)
obsidian_simple_search
simple search for documents matching a specified text query across all files in the vault. use this tool when you want to do a simple text search
obsidian_dataview_search
execute a dataview query language (dql) query.
dql is a powerful, sql-like language for querying obsidian notes based on metadata (frontmatter, inline fields), tags, folders, links, file properties (name, path, dates), and tasks. use it to filter, sort, group, and transform data from your obsidian vault.
**key difference from sql:** dql executes queries sequentially, line by line, passing results between commands. this allows multiple 'where', 'sort', or 'group by' steps, unlike declarative sql.
**finding people/names:**
- search note titles: 'table file.name where contains(file.name, "ben")'
- find notes linking to person: 'list from [[Ben]]'
- search by person tag: 'list from #person/ben'
**common patterns:**
- get note metadata: 'table file.name, file.mtime from "NOTENAME"'
- search by tag: 'list from #tag'
- folder search: 'list from "folder/"'
- backlinks: 'list from [[FILENAME]]'
- all notes: 'list from ""'
this tool is especially good at finding relationships between notes, metadata searches, and structured queries. use it when simple text search doesn't find what you need.
see dataview documentation for full syntax: https://blacksmithgu.github.io/obsidian-dataview/
obsidian_get_file_content
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).
Easy Obsidian Mcp 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 Easy Obsidian Mcp when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.
retrieves the full content of a specific file from the obsidian vault.
obsidian_list_files
lists files and folders within a specified directory in the obsidian vault. if no directory is specified, lists items in the vault root.
obsidian_fuzzy_search
fuzzy search for notes using approximate matching. works even when obsidian api is unavailable. great for finding notes when you're not sure of exact spelling or phrasing.
obsidian_graph_search
analyze links and connections between notes. finds orphaned notes, builds link graphs, and discovers note relationships. works without obsidian api.
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.