Aiven MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIVEN_TOKEN | Yes | The authentication token for Aiven | |
| AIVEN_BASE_URL | No | The Aiven API url | https://api.aiven.io |
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, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_service_details, list_projects, list_services) with clear, descriptive verbs. The naming is uniform and predictable throughout the set.
With only 3 tools, the set feels thin for managing Aiven services, which typically involve operations like create, update, delete, or start/stop. While the tools are well-defined, the count is borderline low for the apparent scope of cloud service management.
The toolset is severely incomplete for Aiven service management, lacking essential CRUD operations (e.g., create_service, update_service, delete_service) and other lifecycle actions (e.g., start, stop, restart). This will cause significant agent failures in handling common workflows.