Aiven MCP Server for Claude
Manage your Aiven cloud database services from Claude — list and monitor PostgreSQL, Apache Kafka, ClickHouse, Valkey, and OpenSearch services, execute SQL queries, manage Kafka topics and schemas, tail logs, and optimize queries — with the official Aiven MCP server.
Open the source and read safety notes before installing.
Safety notes
- Write operations (create/update services, deploy apps) are available but require `AIVEN_READ_ONLY=false` — the server defaults to read-only mode.
- Aiven services include managed production databases — confirm before creating or modifying services.
Privacy notes
- Service metadata, metrics, application logs, PostgreSQL query stats, Kafka topic configurations, and Schema Registry content from your Aiven account are surfaced in Claude's context.
- Your `AIVEN_TOKEN` grants account-level API access — keep it in the MCP config env and never commit it to version control.
Prerequisites
- An Aiven account — sign up at aiven.io.
- An Aiven API token: User Information → Authentication → Generate Token.
- Node.js with `npx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://aiven.io
- Disclosure
- Aiven is a commercial managed database service provider. The MCP server is officially maintained by Aiven.
Full copyable content
{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "<your-token>"
}
}
}
}About this resource
Overview
The Aiven MCP Server is the official Model Context Protocol server from Aiven, the
managed cloud database platform. It gives Claude access to your Aiven projects and services —
PostgreSQL, Apache Kafka, ClickHouse, Valkey (managed Redis), and OpenSearch — for monitoring,
diagnostics, query execution, and configuration management. Two install modes: local npx with
an API token, or the hosted remote endpoint at https://mcp.aiven.live/mcp using OAuth.
Apache-2.0 licensed.
Key capabilities
- Project & service management — list/get/create/update projects and services.
- Service metrics & logs — fetch metrics, application logs, service events, and query activity.
- Apache Kafka — topic CRUD, produce/consume messages, Kafka Connect lifecycle, Schema Registry.
- PostgreSQL — execute SQL queries, query statistics, available extensions, PgBouncer pools, query optimization.
- Applications — deploy and redeploy Aiven applications, manage VCS integrations.
- Cloud & VPC — list available clouds per project, list project VPCs.
- Documentation search — query Aiven knowledge base (hosted server mode).
How it compares
| Server | PostgreSQL | Kafka | ClickHouse | OpenSearch | Notes |
|---|---|---|---|---|---|
| Aiven MCP | Yes | Yes | Yes | Yes | Official, multi-service |
| Confluent MCP | No | Yes | No | No | Kafka-only, official |
| Neon MCP | Yes (Neon) | No | No | No | Serverless Postgres only |
| Turso MCP | No (SQLite) | No | No | No | Edge SQLite only |
Aiven MCP is unique in providing a single interface across multiple managed database types — PostgreSQL, Kafka, ClickHouse, OpenSearch, and Valkey — from one API token.
Installation
Claude Code (stdio with API token)
claude mcp add --scope user aiven-mcp \
-e AIVEN_TOKEN=<your-token> \
-- npx -y mcp-aiven
Claude Code (hosted HTTP with OAuth)
claude mcp add --scope user --transport http aiven-mcp "https://mcp.aiven.live/mcp"
Claude Desktop
{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "<your-token>"
}
}
}
}
Generate your API token at User Information → Authentication → Generate Token in the Aiven Console.
Configuration options
| Env var | Default | Purpose |
|---|---|---|
AIVEN_TOKEN |
— | Required (stdio mode). Aiven API token |
AIVEN_READ_ONLY |
true |
Restrict to read-only operations |
AIVEN_SERVICES_SCOPE |
all | Comma-separated filter: kafka,pg,clickhouse |
Requirements
- An Aiven account with at least one service.
- Node.js (for
npx), or use the hosted remote endpoint. - An MCP client (Claude Code or Claude Desktop).
Security
- Read-only by default — set
AIVEN_READ_ONLY=falseonly when you need write operations. - Use
AIVEN_SERVICES_SCOPEto expose only the service types you need. - Keep
AIVEN_TOKENin the MCP config env; treat it as an account-level secret.
Source Verification Notes
Verified on 2026-06-18:
- Official repository
Aiven-Open/mcp-aiven(Apache-2.0) on npm asmcp-aiven(v1.9.2) documentsnpx -y mcp-aiven,AIVEN_TOKEN/AIVEN_READ_ONLY/AIVEN_SERVICES_SCOPEconfiguration, stdio and hosted HTTP modes, all service categories (PostgreSQL, Kafka, ClickHouse, Valkey, OpenSearch), and the hosted endpoint athttps://mcp.aiven.live/mcp. - Official Aiven MCP documentation at
aiven.io/docs/tools/mcp-server(SSR HTML, HTTP 200) describes the integration setup and credential generation. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the stdio connector pattern used above.
Source citations
Add this badge to your README
How it compares
Aiven MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Aiven MCP Server for Claude Manage your Aiven cloud database services from Claude — list and monitor PostgreSQL, Apache Kafka, ClickHouse, Valkey, and OpenSearch services, execute SQL queries, manage Kafka topics and schemas, tail logs, and optimize queries — with the official Aiven MCP server. Open dossier | CockroachDB Cloud MCP Server for Claude Manage CockroachDB Cloud clusters from Claude — list databases and tables, inspect schemas, run SELECT queries, explain query plans, monitor running queries, and optionally create tables and insert data — with the official CockroachDB Cloud MCP server. Open dossier | Fly.io MCP Server for Claude Manage Fly.io applications, machines, volumes, secrets, certificates, and organizations from Claude — with the official Fly.io MCP server built into the flyctl CLI. Open dossier | Adyen MCP Server for Claude Integrate with Adyen's payment platform from Claude — create payment sessions and links, cancel/refund payments, manage terminals, webhooks, API credentials, and merchant accounts — with the official Adyen Model Context Protocol server covering Checkout and Management APIs. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Aiven | Cockroach Labs | Fly.io | Adyen |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓Write operations (create/update services, deploy apps) are available but require `AIVEN_READ_ONLY=false` — the server defaults to read-only mode. Aiven services include managed production databases — confirm before creating or modifying services. | ✓The server is read-only by default — SELECT, EXPLAIN, and schema queries only; no INSERT, UPDATE, or DELETE. Write tools (create_database, create_table, insert_rows) can be enabled with explicit opt-in — only enable if needed. DROP and TRUNCATE operations are not supported even with write opt-in. | ✓The Fly.io MCP server runs locally with full access to your authenticated Fly.io account — it can create, delete, and modify apps, machines, and secrets. Fly.io warns that running the server remotely can give others access to run commands on your behalf; keep it bound to localhost unless you intend remote access. Destructive operations (machine deletion, secret updates) are available — review Claude's proposed commands before executing in production environments. | ✓This server can create payment sessions, generate payment links, cancel authorized payments, and initiate refunds — these are live financial operations. Use `--env=TEST` during development with Adyen's test API keys to avoid live transactions. Restrict enabled tools to only what is needed via the `--tools` parameter (e.g., `--tools=create_session,list_merchants`). |
| Privacy notes | ✓Service metadata, metrics, application logs, PostgreSQL query stats, Kafka topic configurations, and Schema Registry content from your Aiven account are surfaced in Claude's context. Your `AIVEN_TOKEN` grants account-level API access — keep it in the MCP config env and never commit it to version control. | ✓Database schemas, table structures, query results, and running query metadata from your CockroachDB Cloud cluster are surfaced in Claude's context. Authentication uses OAuth (browser flow) or a service account API key — keep the API key in the MCP config headers. | ✓App names, machine IDs, secret names (not values unless explicitly requested), and log content may be surfaced into Claude's context. Fly.io API tokens (`FLY_ACCESS_TOKEN`) grant full account access — store them in your environment, not in repositories. | ✓Payment session data, merchant account details, terminal configurations, and webhook payloads from your Adyen instance are surfaced in Claude's context. Your Adyen API key is passed as a CLI argument — use environment variable substitution (e.g., `--adyenApiKey=${ADYEN_API_KEY}`) to avoid exposing it in config files. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.