Aiven-Open/mcp-aiven

A Model Context Protocol (MCP) server for the Aiven cloud data platform.
Manage PostgreSQL, Apache Kafka, applications, and other Aiven services directly from AI assistants like Claude, Cursor, and VS Code Copilot.
> [!WARNING]
> **Use with care.** This MCP server can create, modify, and delete Aiven services and data on your behalf. AI agents may execute destructive actions (dropping databases, deleting services, producing messages) based on their interpretation of your prompts. You are fully responsible for the actions taken through this tool.
>
> **Permissions:** Access is governed by the Aiven user permissions associated with the authenticated account. The MCP server can only perform actions that your Aiven user is allowed to do.
>
> **AI Agent Security:** AI agents may need access credentials (database connection strings, streaming tokens) to act on your behalf. Review what your agent is doing, especially in production environments. Follow your organization's security policies and do a risk assessment before giving AI agents access to sensitive resources.
Quick Start
Option 1: Remote (hosted by Aiven)
The MCP server is hosted at https://mcp.aiven.live/mcp. Your MCP client will prompt you to authorize on Aiven.
**Claude Code**
**Cursor**
Or manually add to Cursor MCP settings:
**VS Code / Copilot**
Add to .vscode/mcp.json in your workspace:
Read-Only Mode (Remote)
Enable read-only mode by adding ?read_only=true to the URL. All write operations will be excluded from the MCP:
Scoped Tools (Remote)
Reduce the tool surface exposed to your AI agent by adding ?services_scope= to the URL. Useful when you only work with a subset of Aiven services and want to keep the agent's context focused. Combine values with commas. core (project/service discovery) is always included implicitly.
Valid scopes: all, core, pg, kafka, application, integrations. Use all to explicitly load every tool (same as omitting the param). all cannot be combined with other scopes.
You can also combine with read_only:
Write Exceptions in Read-Only Mode (Remote)
When read_only=true, add ?write_allowlist= to re-enable specific write tools while keeping
everything else read-only. Useful when you want mostly-read access but still need to allow one
write action, for example creating Kafka topics. Combine multiple tool names with commas. Ignored
when read_only is not enabled.
Marketplace Customers (Remote)
If you subscribed to Aiven through a cloud marketplace, add your marketplace as a path segment so sign-in uses the correct console:
| Marketplace | Path segment |
| --- | --- |
| AWS Marketplace | https://mcp.aiven.live/mcp/aws |
| Azure Marketplace | https://mcp.aiven.live/mcp/azure |
| Google Cloud Marketplace | https://mcp.aiven.live/mcp/gcp |
The path segment combines with the query parameters above, for example https://mcp.aiven.live/mcp/gcp?services_scope=pg&read_only=true.
Option 2: stdio (local)
Run the server locally as a child process of your MCP client. Requires Node.js 18+.
You must provide your Aiven API token via the AIVEN_TOKEN environment variable. Create a token here.
**Claude Code**
**Cursor, VS Code** -- add to your MCP client config:
Config file locations:
- Cursor: Cursor Settings > MCP Servers
- VS Code: .vscode/mcp.json in your workspace
Option 3: Local development
Run a local build of the server (useful for development and testing):
The server listens on port 3000 by default. Connect your MCP client to http://localhost:3000/mcp.
To point a remote deployment at a custom host (e.g. your local build), set MCP_HOST:
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
| AIVEN_TOKEN | stdio only | -- | Aiven API token (create one here) |
| AIVEN_READ_ONLY | No | false | Set to true to expose only read-only tools |