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

Google Cloud Run MCPTerraform 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	Google Cloud Run MCPShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Cloud Run services and deploy operations Use for Google Cloud Run application operations.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Deploy/delete/config changes can affect availability, traffic or cloud costs.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Deploy/delete/config changes can affect availability, traffic or cloud costs.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP Google · 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 stars	633 GitHub stars · checked 2026-10-20	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	33,890 package downloads / 30 days · checked 2026-10-20	No reliable download data
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	Google Cloud remote MCP authentication can use OAuth/application credentials or an IAM principal. Cloud Run MCP calls require MCP Tool User permission plus Cloud Run/service-account/artifact permissions appropriate to the requested action.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	Cloud Run is usage billed with free tiers. CPU, memory, requests, outbound data transfer and related networking can become billable beyond allowances.	HCP/TFE/run costs may apply
Permissions	Cloud Run's MCP exposes read tools plus deployment tools. Required IAM roles can include Cloud Run Developer, Service Account User, Artifact Registry Reader and MCP Tool User for deployment workflows.	HCP Terraform/TFE RBAC
Data handling	Not documented in the reviewed sources. The Cloud Run MCP reference does not make a separate MCP-specific retention/training claim; deployment tools can transmit container image references, archives, or inline source content to Google Cloud.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Do not confuse Cloud Run admin MCP with hosting your own MCP on Cloud Run	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	Deployment tools can create/update serving workloads, make services public depending on configuration, change production behavior, and create ongoing cloud spend.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-10-19	2026-07-24
Candidate evidence	2026-10-19	2026-09-25T18:35:00Z

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

Read the evidence method →