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

Upstash 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	Upstash MCPShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Upstash Redis, QStash and Workflow diagnostics and administration Use for Upstash resource operations rather than Context7 documentation.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Some tools can create/delete resources and interact with data; credentials may be sensitive.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Some tools can create/delete resources and interact with data; credentials may be sensitive.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP Upstash · 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	60 GitHub stars · checked 2026-10-20	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	7,264 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	The local package uses Upstash account email plus an API key. Read-only API keys are supported. Upstash also documents hosted/remote connection paths in the current product ecosystem.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	No separate MCP fee is documented. Underlying Upstash services have their own free/paid usage models; the MCP also exposes a temporary free Redis database workflow that expires after 72 hours if not claimed.	HCP/TFE/run costs may apply
Permissions	With a read-only API key, state-modifying tools are disabled while read/query tools remain available.	HCP Terraform/TFE RBAC
Data handling	The server sends anonymous diagnostic information such as SDK/runtime/OS details with requests, but Upstash states it does not collect account data, tool arguments, or tool results through this telemetry. Telemetry can be disabled.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Read-only key hides mutating tools; Box uses separate credentials	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	Full-access credentials can create/delete resources and interact with stored data. The read-only credential mode materially reduces mutation risk.	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 →