home / mcp / aiven mcp server

Aiven MCP Server

Model Context Protocol server for Aiven

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "aiven-open-mcp-aiven": {
      "command": "uv",
      "args": [
        "--directory",
        "$REPOSITORY_DIRECTORY",
        "run",
        "--with-editable",
        "$REPOSITORY_DIRECTORY",
        "--python",
        "3.13",
        "mcp-aiven"
      ],
      "env": {
        "AIVEN_TOKEN": "YOUR_TOKEN",
        "AIVEN_BASE_URL": "https://api.aiven.io"
      }
    }
  }
}

You have an MCP server that enables you to interact with Aiven services (PostgreSQL, Kafka, ClickHouse, Valkey, and OpenSearch) from AI agents. It exposes a compact set of actions to discover projects, list services, and fetch details so your automations can build full-stack solutions without manual browsing.

How to use

Connect to the MCP server through your MCP client and start issuing high-level actions like listing your projects, listing services within a project, and retrieving details for a specific service. You can use these capabilities to discover resources, inspect service configurations, and drive automated workflows. Use the available tools to fetch up-to-date information from Aiven and feed that data into your AI agents for decision making and orchestration.

How to install

Prerequisites you need before starting:

Python 3.13 compatible runtime for MCP (as required by your environment)
A MCP runtime tool named uv available in your environment

Step-by-step installation flow based on the available MCP configurations.

{
  "mcpServers": {
    "mcp-aiven": {
      "command": "uv",
      "args": [
        "--directory",
        "$REPOSITORY_DIRECTORY",
        "run",
        "--with-editable",
        "$REPOSITORY_DIRECTORY",
        "--python",
        "3.13",
        "mcp-aiven"
      ],
      "env": {
        "AIVEN_BASE_URL": "https://api.aiven.io",
        "AIVEN_TOKEN": "$AIVEN_TOKEN"
      }
    }
  }
}

Additional installation notes

If you are using a client that supports an alternate configuration (for example a different UI or environment), you can apply the same MCP command scaffolding. Ensure you replace placeholder variables with your actual values before starting the MCP server.

Environment and start notes

The following environment variables are required to configure the Aiven connection: - AIVEN_BASE_URL: The Aiven API URL - AIVEN_TOKEN: The authentication token for your Aiven account These variables should be available in your runtime environment when you start the MCP server.

Security considerations

MCP servers run in your environment, so you own and control their security. Treat API tokens with care, grant the minimum permissions required, rotate tokens regularly, and avoid exposing credentials to AI agents or external services. Follow the principle of least privilege for all tokens and credentials used by the MCP server.

Troubleshooting and notes

If the MCP server fails to start, verify that the environment variables are correctly set and that the path to the repository is accessible. Check that the uv runtime is available and that you are using the exact command and arguments shown for your configuration. Restart the MCP server after any changes to environment variables or command paths.

Tools exposed by this MCP server

The server provides programmatic access to the following actions: - list_projects: List all projects on your Aiven account. - list_services: List all services in a specific Aiven project. - get_service_details: Get the details of a specific service within a project.

Available tools

list_projects

List all projects on your Aiven account.

list_services

List all services in a specific Aiven project.

get_service_details

Get the detail of your service in a specific Aiven project.