Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

MCPVault for ObsidianExcel MCP Server

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedFirecrawl MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	MCPVault for ObsidianMCP100 Selected	Excel MCP ServerMCP100 Selected
Task fit
Best for	Obsidian users who want local search and supervised note maintenance Vaults protected by version control or reliable backups Users able to expose only a dedicated, bounded vault	Reading, creating, formatting, charting, and updating XLSX workbooks and worksheets, including formulas and pivot tables
Not ideal for	Unbacked-up personal knowledge bases Read-only research where a simpler filesystem search is sufficient Enterprise knowledge requiring centralized authorization and audit controls	Workbooks that depend on full desktop Excel behavior, macros, or manual visual review
Avoid when	The vault contains secrets, regulated data, or material that cannot reach the selected AI provider Write, move, and delete tools cannot be confirmed by a human The vault path cannot be narrowed to a dedicated directory	You cannot restrict file access or are using a version affected by CVE-2026-40576
Provenance
Provenance details	Community implementation BitBonsai · Publisher source ↗	Community implementation Haris Musa · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 13, 2026 Package: Aug 9, 2026	Repo: Apr 12, 2026 Package: Apr 12, 2026
Popularity evidence
GitHub stars	1,613 GitHub stars · checked 2026-08-14T18:46:26.000Z	4,108 GitHub stars · checked 2026-08-14T18:46:26.000Z
30-day package downloads	64,139 30-day package downloads · checked 2026-08-14T18:46:26.000Z	No reliable download data
External adoption evidence	github: repository stars: 1,613Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗	github: repository stars: 4,108Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	None at the local stdio layer.	Local stdio has no separate service authentication. Remote MCP authentication is not documented, so remote listeners must remain network-restricted.
Cost	MCPVault is MIT licensed and free to run locally. MCP-host, model, backup, and storage costs remain.	The MIT-licensed local server lists no usage fee; normal hosting, client, model, and network costs may apply.
Permissions	The server has filesystem read and write access within the supplied vault root, including note creation, overwrite or patch, frontmatter changes, moves, tags, and deletion. Operating-system permissions and the configured vault path are the primary boundary.	The server can read, create, modify, format, chart, and delete workbook content. Remote modes confine relative paths to EXCEL_FILES_PATH in the patched release.
Data handling	Vault content and metadata are read locally and returned to the MCP client and model. Changes are written directly to local files. MCPVault states that it does not receive, store, or transmit vault data, while the selected AI provider still processes content sent by the client.	Workbook paths and spreadsheet content are processed by the server and returned to the connected client as required by tool calls; publisher telemetry and retention are not documented.
Limitations
Tradeoffs	Local stdio avoids a hosted MCP service, but note contents still enter the MCP host and model context. Frontmatter-aware writes are more useful than generic file access but increase integrity risk. npx makes setup simple, while stricter environments may prefer a pinned and reviewed package version.	It provides deep spreadsheet manipulation without desktop Excel, but write tools can overwrite data and remote transports add network and filesystem exposure.
Risk context	A selected vault can contain a large body of private knowledge, and write tools can overwrite, move, or delete it. Use a dedicated vault, reliable backups or version control, an absolute path, a reviewed package version, and explicit approval for writes.	Versions through 0.1.7 have a critical path-traversal vulnerability. Use 0.1.8 or later, prefer stdio, restrict workbook paths, avoid public remote listeners, and keep recoverable backups.
Evidence date
Editorial review	2026-07-24	2026-08-13
Candidate evidence	2026-08-14T18:46:26.000Z	2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →