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.
| Evidence field | Aiven MCPShortlist candidate | Terraform MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Aiven · 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 | 28 GitHub stars · checked 2026-10-20 | 1,534 GitHub stars · checked 2026-09-25T18:35:00Z |
| Package downloads / 30 days | 1,232 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 | Hosted Aiven MCP prompts the user to authorize with Aiven; local stdio mode uses an Aiven API token. | HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN |
| Cost | The MCP can query Aiven plan pricing, and creating/updating services can create normal Aiven service charges. Aiven offers free and paid service plans depending on product/configuration. | HCP/TFE/run costs may apply |
| Permissions | Access is governed by the authenticated Aiven user's permissions. The hosted MCP supports read-only mode, service-scope filtering, and an explicit write allow-list for selectively re-enabling individual writes. | HCP Terraform/TFE RBAC |
| Data handling | Aiven warns that agents may need service access credentials such as database connection strings or streaming tokens to act on the user's behalf. The reviewed README instructs users to assess production and sensitive-resource exposure. | registry/HCP/TFE data may reach connected MCP client/LLM |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Aiven explicitly warns that the MCP can create, modify and delete services/data, drop databases, delete services and produce messages. Those actions can be destructive and can incur cloud-service cost. | 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 →