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

buildkiteTerraform 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	buildkiteMCP100 Recommended	Terraform MCPMCP100 Recommended
Task fit
Best for	CI/CD investigation and controlled Buildkite operations through hosted or self-managed MCP transports.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Teams outside the publisher ecosystem or without least-privilege credentials	Users who need a fully reviewed MCP100 recommendation today
Avoid when	The connected identity is broader than the task requires Tool calls cannot be reviewed before consequential mutations	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP ecosystem:buildkite · Publisher source ↗	First-party MCP HashiCorp · Publisher source ↗
Maintenance
Maintenance details	Repo: Sep 24, 2026 Package: Not documented	Repo: Aug 14, 2026 Package: Not documented
Popularity evidence
GitHub stars	54 GitHub stars · checked 2026-09-24T04:14:26.327000Z	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	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	Hosted access uses short-lived OAuth, while headless and local deployments use scoped Buildkite API tokens.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.	HCP/TFE/run costs may apply
Permissions	OAuth and API-token scopes govern organization, pipeline, build, job, artifact, and Test Engine access; a read-only hosted endpoint is available.	HCP Terraform/TFE RBAC
Data handling	Authorized 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.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Write-capable endpoints can rerun, cancel, or otherwise change CI state; use the read-only endpoint for investigation.	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	Write-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.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-07-30	2026-07-24
Candidate evidence	2026-09-24T04:25:05.554391Z	2026-09-25T18:35:00Z

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

Read the evidence method →