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

Zapier MCPCodebase Memory MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Zapier MCPShortlist candidate	Codebase Memory MCPMCP100 Recommended
Task fit
Best for	Let an AI client execute selected Zapier actions across connected apps Zapier users who need to let an ai client execute selected zapier actions across connected apps.	Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for	Each user/server has a generated secure URL and a user-selected action set, so there is no universal endpoint or fixed tool count. Actions can create broad external side effects across connected services and should be narrowly scoped and confirmed.	Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when	Each user/server has a generated secure URL and a user-selected action set, so there is no universal endpoint or fixed tool count. Actions can create broad external side effects across connected services and should be narrowly scoped and confirmed.	The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details	First-party MCP Zapier · Publisher source ↗	First-party MCP DeusData · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Aug 14, 2026
Popularity evidence
GitHub stars	Not documented	44,904 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	No reliable download data	28,000 package downloads / 30 days · checked 2026-08-14T00:00:00.000Z
Shared repository stars	443 Shared repository stars (not MCP-specific) · checked 2026-10-20	Not documented
External adoption evidence	Not documented	npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	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 user creates/connects a Zapier MCP server and signs in to Zapier from the MCP client; Zapier manages connected-app credentials behind the selected tools.	local stdio; no remote auth needed
Cost	Each successful Zapier MCP tool call uses two tasks from the Zapier plan allowance; failed tool calls do not consume tasks. Zapier also has free and paid plans.	none beyond local resources
Permissions	Each MCP server exposes a user-selected set of Zapier actions rather than a universal fixed tool set. A fixed tool bundle can be used for tightly scoped access.	reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handling	Zapier handles the credentials and rate limits for connected apps. The reviewed MCP page does not state a separate MCP-specific prompt/result retention or training policy.	local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs	First-party documentation establishes Zapier MCP, its dynamic secure URL model, and cross-app action scope. Exact tool inventory is user-configured, and runtime context footprint remains unmeasured.	Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed. Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk context	Zapier MCP can create broad external side effects across connected services—for example sending messages, creating records/events/issues, or triggering other app actions. The actual risk depends on the configured action set.	latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review	2026-10-19	2026-09-23
Candidate evidence	2026-10-20	2026-09-25T18:35:00Z

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

Read the evidence method →