Aiven MCP Server
Related Servers
Alternatives to Aiven MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceProvides access to Aiven's PostgreSQL, Kafka, ClickHouse, Valkey and OpenSearch services, enabling LLMs to build full stack solutions by interacting with the Aiven ecosystem.3Apache 2.0
- AlicenseDqualityDmaintenanceA Model Context Protocol server that provides access to Aiven's managed services (PostgreSQL, Kafka, ClickHouse, Valkey, OpenSearch) and connectors, enabling LLMs to build full stack solutions.3Apache 2.0

Aiven MCP Serverofficial
AlicenseDqualityBmaintenanceA Model Context Protocol server that provides access to Aiven services (PostgreSQL, Kafka, ClickHouse, Valkey, OpenSearch), enabling LLMs to build full stack solutions by interacting with these services.3632 npm28Apache 2.0- AlicenseBqualityBmaintenanceEnables AI assistants to manage a self-hosted PaaS by listing projects and services, reading deployment and container logs, and deploying, restarting, or updating environment variables for applications and compose services.322Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and manage hosted PocketBase projects, instances, deployments, domains, logs, and diagnostics. It supports OAuth or CLI-token access with read-only or scoped permissions and optional database tools.Apache 2.0

@avala-ai/mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceLets AI assistants interact with Avala's Physical AI data platform to browse and manage sensor datasets, annotation projects, exports, tasks, and storage connections through tool calls.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_service_details retrieves specific service information, list_projects enumerates projects, and list_services enumerates services. There is no overlap in functionality, and an agent can easily distinguish between them based on their names and inferred purposes.
All tool names follow a consistent verb_noun pattern using snake_case: get_service_details, list_projects, and list_services. The naming is predictable and readable, with no deviations or mixed conventions.
With only 3 tools, the server feels under-scoped for managing Aiven services, which typically involve operations like creating, updating, deleting, or configuring services and projects. This minimal set lacks essential CRUD operations, making it too thin for the apparent domain.
The tool surface is severely incomplete for cloud service management. It only provides read-only operations (get and list) with no ability to create, update, or delete services or projects. This leaves significant gaps that will cause agent failures in common workflows.