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 fieldTerraform MCPMCP100 RecommendedbuildkiteMCP100 Recommended
Task fit
Best for
  • Connect compatible AI clients to HashiCorp's documented MCP capabilities.
  • CI/CD investigation and controlled Buildkite operations through hosted or self-managed MCP transports.
Not ideal for
  • Users who need a fully reviewed MCP100 recommendation today
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Permissions, credentials, and connected data cannot be tested with least privilege
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

HashiCorp · Publisher source ↗

First-party MCP

ecosystem:buildkite · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 14, 2026

Package: Not documented

Repo: Sep 24, 2026

Package: Not documented

Popularity evidence
GitHub stars

1,534

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

54

GitHub stars · checked 2026-09-24T04:14:26.327000Z

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✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationHCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKENHosted access uses short-lived OAuth, while headless and local deployments use scoped Buildkite API tokens.
CostHCP/TFE/run costs may applyThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsHCP Terraform/TFE RBACOAuth and API-token scopes govern organization, pipeline, build, job, artifact, and Test Engine access; a read-only hosted endpoint is available.
Data handlingregistry/HCP/TFE data may reach connected MCP client/LLMAuthorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive cloud & devops information.
Limitations
Tradeoffs
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
  • Write-capable endpoints can rerun, cancel, or otherwise change CI state; use the read-only endpoint for investigation.
Risk contextstdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by defaultWrite-capable endpoints can rerun, cancel, or otherwise change CI state; use the read-only endpoint for investigation. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-07-242026-07-30
Candidate evidence2026-09-25T18:35:00Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →