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

Appwrite 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	Appwrite MCPShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Appwrite project, database, authentication and storage administration Use for Appwrite backend development and administration.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Administrative APIs touch users, application data and secrets.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Administrative APIs touch users, application data and secrets.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP Appwrite · 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	73 GitHub stars · checked 2026-10-20	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Package downloads / 30 days	132,125 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	Browser-based OAuth/consent flow; the user approves scopes and no API key needs to be copied into the MCP client.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	Appwrite's reviewed MCP material says availability is tied to Pro/Max plans, while the broader Appwrite service has paid resource usage and overage pricing.	HCP/TFE/run costs may apply
Permissions	The Appwrite MCP operates within the approved scopes/account. Appwrite notes that adding custom connectors on Team and Enterprise plans requires an organization Owner.	HCP Terraform/TFE RBAC
Data handling	Not documented in the reviewed sources. The reviewed Appwrite MCP README does not provide a clear MCP-specific retention/training statement.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Exact tool inventory/scope varies; hosted OAuth recommended	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	Appwrite administrative/project APIs can touch users, application data, services and configuration. The consequence of a tool call depends on the OAuth scopes granted.	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 →