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, and an agent can easily distinguish between them based on their names and inferred actions.
All tool names follow a consistent verb_noun pattern: get_service_details, list_projects, and list_services. The naming is uniform, using snake_case throughout, with clear verbs (get, list) that accurately describe the actions.
With only 3 tools, the server feels thin for managing Aiven services, which typically involve CRUD operations. While the tools cover listing and getting details, the absence of create, update, or delete tools suggests limited scope, making it borderline appropriate for the domain.
The tool surface is significantly incomplete for managing Aiven services. It lacks essential operations such as creating, updating, or deleting services or projects, leaving agents unable to perform full lifecycle management. This gap will likely cause agent failures in handling common administrative tasks.