← Back to directory
A

Aiven MCP Server

Official
Manage the Aiven cloud data platform from your AI assistant
Category
Database #13 of 58
Stars
★ 28 Popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js 18+ · Hosted (no local runtime)
Credentials
API key / credential required
License
Apache-2.0
Last commit
Tools
46
64FMRS · C

An officially maintained, mature MCP server with comprehensive tool coverage (projects, service lifecycle, Kafka, PostgreSQL, application deployment) and solid safety controls such as read-only mode, tool scoping, and a write allowlist — a strong fit for Aiven customers managing their data infrastructure through AI assistants.

Strongest · Documentation 16/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
11/20
Maintenance
13/20
Documentation
16/20
Setup experience
14/20
Why each score
Reliability 10/20
The README's tool tables (Core/Kafka/PostgreSQL/Applications/Documentation) line up descriptively with the npm package and remote streamable-http endpoint declared in server.json, and the environment-variable gating logic (AIVEN_READ_ONLY, AIVEN_SERVICES_SCOPE, AIVEN_ALLOW_SECRETS) is described consistently. However, no CI workflow files or test code are present in the supplied evidence, so the MCP init/tool-list handshake and the match between declared and actual behavior cannot be verified as reproducible. Per the static calibration rule, reliability is capped at 12 without verifiable execution evidence, so 10 is given, reflecting a plausible happy path with unverified edge-case and error handling.
Security and permissions 11/20
The server exposes high-risk operations — aiven_pg_write (arbitrary SQL writes), aiven_service_update/create, aiven_kafka_topic_delete, aiven_kafka_topic_message_produce, aiven_application_deploy — all available by default (AIVEN_READ_ONLY unset), with no built-in per-action confirmation step; the README explicitly states the user is 'fully responsible' for destructive actions taken by the agent. Mitigations are concrete, though: opt-in read-only mode with a write_allowlist exception mechanism, tool-surface scoping (services_scope), credential redaction by default in the connection-info tool (requiring explicit AIVEN_ALLOW_SECRETS, and disabled entirely in read-only mode), plus rate limiting and optional edge-auth protection for the remote deployment. Permissions are inherited from the underlying Aiven account (partial least-privilege). Because the main risks are disclosed and mitigated at the configuration level, but the server itself lacks enforced confirmation for destructive calls, this falls short of the red-line threshold (0-4) but also short of a fully mature confirmation model — scored 11.
Maintenance 13/20
The repository is maintained under the official Aiven-Open organization (vendor-backed), and the version field (1.11.2) indicates multiple prior releases. License is clearly Apache-2.0, and the README references a CONTRIBUTING.md, indicating an established contribution process. The supplied evidence does not include a SECURITY.md or an explicit security-response channel, and with only 26 stars and 5 open issues, issue-response cadence and community activity cannot be assessed from the given material. Scored 13: clear ownership and version history, but governance documentation (security response, release cadence) has gaps.
Documentation 16/20
The README is well-layered: it documents both remote (OAuth-hosted) and local stdio setup paths with concrete config snippets for Claude Code, Cursor, and VS Code; a complete environment-variable table with requiredness and defaults; tools grouped and described by functional area (Core/Kafka/PostgreSQL/Applications/Documentation); and a dedicated section on edge-protection rollout steps and rate-limit parameters. Gaps: there is no dedicated troubleshooting section, and cost implications of triggering real cloud resource creation/changes are not discussed beyond a general risk warning. Scored 16.
Setup experience 14/20
Two clear setup paths are given: a one-command remote add for Claude Code (or a JSON snippet for Cursor/VS Code) requiring no local build, and a one-line npx invocation plus an AIVEN_TOKEN env var for local stdio use, with few steps and cross-platform compatibility (Node.js 18+). Marketplace-specific paths (AWS/Azure/GCP) are also documented. However, no CI or test evidence in the supplied material verifies these install paths are exercised automatically, so per the static calibration rule setup is capped at 15 — scored 14.

Static review · not runListed 2026-09-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account dataConnects to a database

Best for

  • Developers and ops teams already on Aiven who want AI-assisted resource management
  • Teams managing both PostgreSQL and Kafka
  • Security-conscious users who want a reduced tool surface (read-only, scoped)

Not for

  • Users not on the Aiven platform
  • Production environments where AI agents must not perform destructive actions (dropping databases, deleting services)
  • Self-hosted/local deployments, which cannot use the aiven_docs_search tool

Required permissions

  • Local stdio mode requires an Aiven API token (AIVEN_TOKEN)
  • Remote mode uses OAuth authorization; access is governed by the Aiven user permissions of the authenticated account
  • The server can only perform actions the Aiven user is allowed to do

Risks and side effects

  • AI agents may execute destructive actions (dropping databases, deleting services, producing messages) based on their interpretation of prompts
  • With AIVEN_ALLOW_SECRETS enabled, the connection-info tool returns live credentials (passwords, connection URIs, certs) into the conversation
  • Review agent behavior, perform a risk assessment, and follow your organization's security policies before using in production

Setup

Before you start

Runtime:Node.js 18+ · Hosted (no local runtime)

AIVEN_TOKEN requiredsecret Aiven API token (required for local stdio mode); create one at https://console.aiven.io/profile/tokens.
MCP_EDGE_AUTH_SECRET optionalsecret Shared secret that must match the X-Edge-Auth value injected by Cloudflare; required when EXTRA_PROTECTION=true.
Other optional settings (9)
AIVEN_READ_ONLY optional Set to true to expose only read-only tools; defaults to false.
AIVEN_SERVICES_SCOPE optional Comma-separated tool scopes (pg, kafka, application, integrations, core, all) to limit the exposed tool surface.
AIVEN_ALLOW_SECRETS optional Set to true to let the connection-info tool return live credentials instead of [REDACTED]; defaults to false.
AIVEN_WRITE_ALLOWLIST optional Comma-separated tool names re-enabled while read-only mode is on.
MCP_HOST optional Overrides the OAuth protected resource host; defaults to https://mcp.aiven.live.
MCP_TRANSPORT optional Transport mode; defaults to stdio, set to http to start an HTTP server.
MCP_HTTP_RATE_LIMIT_MAX optional Max POST /mcp requests per bearer token per window on HTTP transport; defaults to 1000.
MCP_HTTP_RATE_LIMIT_WINDOW_MS optional Rate-limit window length in milliseconds; defaults to 60000.
EXTRA_PROTECTION optional Set to true on HTTP deployments to require a valid X-Edge-Auth header on every request except GET /health.

Remote (recommended): run claude mcp add --scope user --transport http aiven-mcp "https://mcp.aiven.live/mcp" in Claude Code, or add the URL in Cursor / VS Code MCP settings; the client will prompt you to authorize on Aiven via OAuth. Local stdio: requires Node.js 18+; create an API token at https://console.aiven.io/profile/tokens, then run claude mcp add --scope user aiven-mcp -e AIVEN_TOKEN=your-token-here -- npx -y mcp-aiven, or configure command npx with args ["-y","mcp-aiven"] and the AIVEN_TOKEN environment variable. Tool surface can be controlled via AIVEN_READ_ONLY, AIVEN_SERVICES_SCOPE, and related variables or URL query parameters.

.mcp.json
{"mcpServers":{"aiven-mcp":{"command":"npx","args":["-y","mcp-aiven"],"env":{"AIVEN_TOKEN":"your-token-here"}}}}

Shown for Claude Code. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "aiven-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-aiven"
      ],
      "env": {
        "AIVEN_TOKEN": "your-token-here"
      }
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add aiven-mcp -e AIVEN_TOKEN=your-token-here -- npx -y mcp-aiven

Run it in a terminal; replace any <…> placeholders with your own values first.

Check that it works

After connecting, check that tools like aiven_project_list appear in the client's tool list, or simply ask 'List my Aiven projects' — a returned project list confirms the connection works.

Troubleshooting

  1. Verify AIVEN_TOKEN is set correctly and valid (required for stdio mode)
  2. Local execution requires Node.js 18+
  3. Remote mode requires completing Aiven OAuth authorization in your MCP client
  4. If tools seem missing, check whether services_scope limits the exposed scope
  5. Cloud marketplace customers (AWS/Azure/GCP) must add the marketplace path segment, e.g. /mcp/aws

Things to try

Once connected, you can ask your AI assistant things like:

  • List all of my Aiven projects.
  • Create a new Kafka topic and then read the messages currently in it.
  • Show the query statistics for my PostgreSQL service and suggest optimizations.
  • Change my service plan to a higher tier and show the pricing.

Tools 46

aiven_project_list read-only
List projects
aiven_project_get read-only
Get project details
aiven_list_project_clouds read-only
List cloud platforms for a project
aiven_project_vpc_list read-only
List VPCs for a project
aiven_service_list read-only
List services
aiven_service_type_plans read-only
List plans with cloud availability
aiven_service_plan_pricing read-only
Get pricing for a plan in a specific cloud
aiven_service_create writes
Create a service
Show 38 more tools
aiven_service_get read-only
Get service information
aiven_service_update writes
Update a service (plan, config, power state)
aiven_service_metrics_fetch read-only
Fetch metrics for managed data services
aiven_service_application_metrics_get read-only
Fetch metrics for application services
aiven_project_get_service_logs read-only
Get service log entries
aiven_service_query_activity read-only
Fetch current queries for a service
aiven_project_get_event_logs read-only
Get project event log entries
aiven_kafka_topic_list read-only
List Kafka topics
aiven_kafka_topic_create writes
Create a Kafka topic
aiven_kafka_topic_get read-only
Get Kafka topic info
aiven_kafka_topic_update writes
Update a Kafka topic
aiven_kafka_topic_delete destructive
Delete a Kafka topic
aiven_kafka_topic_message_list read-only
Read messages from a Kafka topic
aiven_kafka_topic_message_produce destructive
Produce messages into a Kafka topic
aiven_kafka_connect_available_connectors read-only
List available connector types
aiven_kafka_connect_list read-only
List running connectors
aiven_kafka_connect_create_connector writes
Create a connector
aiven_kafka_connect_edit_connector writes
Edit a connector
aiven_kafka_connect_get_connector_status read-only
Get connector status
aiven_kafka_connect_pause_connector writes
Pause a connector
aiven_kafka_connect_resume_connector writes
Resume a connector
aiven_kafka_connect_restart_connector writes
Restart a connector
aiven_kafka_connect_delete_connector destructive
Delete a connector
aiven_kafka_schema_registry_subjects read-only
List Schema Registry subjects
aiven_kafka_schema_registry_subject_version_get read-only
Get a Schema Registry subject version
aiven_pg_service_available_extensions read-only
List available PostgreSQL extensions
aiven_pg_service_query_statistics read-only
Fetch query statistics
aiven_pg_bouncer_create writes
Create a PgBouncer connection pool
aiven_pg_bouncer_update writes
Update a PgBouncer connection pool
aiven_pg_bouncer_delete destructive
Delete a PgBouncer connection pool
aiven_pg_read read-only
Run a read-only SQL query
aiven_pg_write destructive
Run a write SQL statement (INSERT, UPDATE, DELETE, CREATE TABLE, etc.)
aiven_pg_optimize_query read-only
AI-powered query optimization (EverSQL)
aiven_application_deploy writes
Deploy a Dockerized application to Aiven
aiven_application_redeploy writes
Rebuild and redeploy an existing application
aiven_vcs_integration_list read-only
List connected VCS (GitHub) accounts
aiven_vcs_integration_repository_list read-only
List repositories for a VCS integration
aiven_docs_search read-only
Search official Aiven documentation in natural language (hosted server only)

Use cases

Provision and manage PostgreSQL services through an AI assistant
Manage Apache Kafka topics, messages, and Connect connectors in natural language
Inspect service metrics, logs, query activity, and project events
Deploy and redeploy Dockerized applications
Safely browse Aiven projects and services in read-only mode

Supported clients

Claude Code
Cursor
VS Code

Listed from the project's documentation, not tested by this site.

Overview

Aiven MCP Server is an officially maintained Model Context Protocol server for the Aiven cloud data platform. It lets AI assistants such as Claude, Cursor, and VS Code Copilot provision and manage PostgreSQL, Apache Kafka, and application deployments directly. It can run in two ways: as an Aiven-hosted remote HTTP server (OAuth authorization at https://mcp.aiven.live/mcp) or locally via npx mcp-aiven over stdio (requires Node.js 18+ and an AIVEN_TOKEN API token). It supports read-only mode, tool scoping by service (pg, kafka, application, integrations, core), and a write allowlist.

Similar servers

Source revision 4180f01d817d Data synced 2026-10-19 Read the FMRS scoring method