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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldZapier MCPShortlist candidateTerraform 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.
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
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.
  • Users who need a fully reviewed MCP100 recommendation today
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.
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

Zapier · Publisher source ↗

First-party MCP

HashiCorp · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

1,534

GitHub stars · checked 2026-09-25T18:35:00Z

Shared repository stars

443

Shared repository stars (not MCP-specific) · checked 2026-10-20

Not documented
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe 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.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
CostEach 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.HCP/TFE/run costs may apply
PermissionsEach 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.HCP Terraform/TFE RBAC
Data handlingZapier 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.registry/HCP/TFE data may reach connected MCP client/LLM
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.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextZapier 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.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-10-192026-07-24
Candidate evidence2026-10-202026-09-25T18:35:00Z

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

Read the evidence method →