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

Office Editor MCPCodebase Memory

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	Office Editor MCPWatchlist candidate	Codebase MemoryMCP100 Selected
Task fit
Best for	Creating, reading, formatting, and editing DOCX Word documents Evaluating separately configured XLSX and PPTX authoring servers in a disposable local workspace	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	A packaged, versioned MCP installation with one cohesive server surface Legacy DOC, XLS, or PPT support without the separately documented Windows and Microsoft Office path	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	The server would have write access outside a dedicated non-sensitive document directory You cannot isolate optional translation, database, OCR, encryption, or destructive file operations	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	Community implementation theWDY · Publisher source ↗	Community implementation io.github.DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 13, 2026 Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	91 GitHub stars · checked 2026-08-14T18:46:26.000Z	38,935 GitHub stars · checked 2026-08-14T18:46:26.000Z
30-day package downloads	No reliable download data	28,015 30-day package downloads · checked 2026-08-14T18:46:26.000Z
External adoption evidence	github: repository stars: 91Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗	github: repository stars: 38,935Exact 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	The local stdio servers have no separate authentication. Optional translation and database integrations accept their own API keys or connection strings, which must stay in local configuration.	No authentication or API key is documented for local stdio. CBM_ALLOWED_ROOT is an optional filesystem containment control; no containment is imposed when it is unset.
Cost	The MIT-licensed source has no documented MCP usage fee. Microsoft Office-dependent features, translation APIs, databases, OCR, and client services may have separate costs.	The MIT-licensed native software lists no service fee. Local storage and package-manager costs are separate.
Permissions	The servers can read, create, format, overwrite, copy, and in some modes move or delete local documents. OFFICE_EDIT_PATH scopes general operations and OFFICE_ALLOW_DESTRUCTIVE gates move/delete behavior.	Indexes repositories, queries code and graphs, performs architecture and impact analysis, manages ADRs and watchers, deletes projects, and writes agent configuration, instruction, Skill, and hook files.
Data handling	Office files are processed locally by default. Optional translation, OCR, database import/export, and other integrations can send or retrieve content through configured external services.	The publisher says processing is local and code does not leave the machine. Indexes, embeddings, memories, SQLite data, and logs persist under the local CBM cache directory.
Limitations
Tradeoffs	The repository covers many Office operations, but users must install from source and configure Word, Excel, PowerPoint, and general operations separately. Recent path and destructive-action controls reduce risk without replacing package provenance and independent advisory review.	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed.
Risk context	Clone a reviewed revision, install in an isolated environment, set OFFICE_EDIT_PATH to a disposable directory, keep destructive operations disabled, and configure only the single Office server needed for the task.	Indexing can capture sensitive files, while persistent graph data and installer/configuration writes expand local exposure. Set CBM_ALLOWED_ROOT, protect the cache, and use explicit project paths.
Evidence date
Editorial review	2026-08-14	2026-08-11
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 →