Aiven MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIVEN_TOKEN | Yes | The authentication token | |
| AIVEN_BASE_URL | Yes | The Aiven API url |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsD | – |
| list_servicesD | – |
| get_service_detailsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.