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 fieldNetlify MCPShortlist candidateTerraform MCPMCP100 Recommended
Task fit
Best for
  • Create, deploy, inspect, and configure applications hosted on Netlify.
  • Teams already using Netlify that can test with non-sensitive data and least privilege.
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for
  • Users who need an MCP100-recommended recommendation today
  • Unattended production workflows before permissions and failure behavior are reviewed
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • The connected data or account cannot be safely exposed to the selected AI client
  • You cannot verify least-privilege access and review write-capable tool calls
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

First-party MCP

Netlify · Publisher source ↗

First-party MCP

HashiCorp · Publisher source ↗

Maintenance
Maintenance details

Repo: Jul 28, 2026

Package: Jul 28, 2026

Repo: Aug 14, 2026

Package: Not documented

Popularity evidence
GitHub stars

63

GitHub stars · checked 2026-09-24T00:00:00.000Z

1,534

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

Package downloads / 30 days

15,719

package downloads / 30 days · checked 2026-07-29T17:30:00.000Z

No reliable download data
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 noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationAuthentication follows the publisher's documented endpoint or local-server configuration. OAuth scopes, API-key handling, and revocation behavior remain review items.HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
CostNo MCP100 cost conclusion is published yet. The publisher's account plan, API usage, infrastructure, or per-action charges may apply.HCP/TFE/run costs may apply
PermissionsExact permissions and the read/write boundary have not yet completed MCP100 independent review; consult the linked publisher sources and use the narrowest available scope.HCP Terraform/TFE RBAC
Data handlingPublisher-accessible account or application data may be returned to the MCP client and its selected model. Retention and subprocess behavior require candidate-specific review.registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs
  • First-party provenance and a clear task improve confidence, but do not replace an independent permissions and usability review.
  • Client transport compatibility does not prove that authentication, scopes, failure handling, and every tool behave safely.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextUse a test workspace or non-production account, least privilege, read-only controls where available, explicit approval for mutations, and credential revocation after evaluation.stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-09-24T00:00:00.000Z2026-09-25T18:35:00Z

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

Read the evidence method →