MCP100 verdict
Not currently recommended. Shortlist — editorially admitted, not a Recommended endorsement.
MCP100 Assessment
Editorial verdict
Reviewed October 19, 2026
Task Fit
Mapped
Specialized workflows
Trust
Status warning
Use ?read_only=true and ?services_scope=...; secret exposure opt-in only
Maintenance
Date unavailable
No dated repository or package update is currently stored.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Evidence scope
28 MCP repository stars
1.2k package downloads / 30 days
Repository identity: Aiven-Open/mcp-aiven
Package identity: mcp-aiven · version 1.18.0
Stars observed October 20, 2026 · Downloads observed October 20, 2026
Exact current first-party MCP repository; stars are MCP-specific repository evidence.
Exact MCP-specific npm package; 30-day downloads are directly attributable to this MCP package.
Publisher activity observed October 19, 2026
Current source snapshot
Source relationship: First-party MCP
Reviewed October 19, 2026
Evidence-backed setup
Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.
Transport not recorded
Complete client-specific setup, verification and removal are not documented in this reviewed source.
Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.
Evidence checked 2026-10-19
Type-appropriate, source-backed setup for this mcp server profile.
Loading optional publisher installation details…
{"url":"https://mcp.aiven.live/mcp"}Capability
Aiven MCP is a Aiven MCP integration for aiven managed data services and troubleshooting. Use when managing Aiven services. Cloud resource changes, access grants and database logs can be sensitive.
services_scope and read_only flags change the number of tools; no universal count
Not measured yet
Estimated token footprint of the MCP tool schemas exposed to the agent.
https://mcp.aiven.live/mcp
Reviewed access
Reviewed sources
Related reviewed MCPs
Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.
Choose this instead if
Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.
Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.
Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Choose this instead if
Choose Terraform MCP instead if connect compatible AI clients to HashiCorp's documented MCP capabilities.
Recommended after reviewed Batch 1 correction: exact 61-tool contract closes the prior formal Recommended gap.
Connect agents to Azure resources and more than forty Azure services.
Choose this instead if
Choose Azure MCP Server instead if discovering and inspecting resources across supported Azure services.
Connect agents to Azure resources and more than forty Azure services.
Aiven is listed as First-party MCP in MCP100’s current evidence.
Current official resources:
From the publisher README
Original client setup and configuration retained from the publisher documentation.
Publisher-documented clients
These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.
The MCP server is hosted at https://mcp.aiven.live/mcp. Your MCP client will prompt you to authorize on Aiven.
Claude Code
claude mcp add --scope user --transport http aiven-mcp "https://mcp.aiven.live/mcp"
Cursor
Or manually add to Cursor MCP settings:
{
"mcpServers": {
"aiven-mcp": {
"url": "https://mcp.aiven.live/mcp"
}
}
}
VS Code / Copilot
Add to .vscode/mcp.json in your workspace:
{
"servers": {
"aiven-mcp": {
"type": "http",
"url": "https://mcp.aiven.live/mcp"
}
}
}
Enable read-only mode by adding ?read_only=true to the URL. All write operations will be excluded from the MCP:
{
"mcpServers": {
"aiven-mcp": {
"url": "https://mcp.aiven.live/mcp?read_only=true"
}
}
}
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, opensearch. Use all to explicitly load every tool (same as omitting the param). all cannot be combined with other scopes. opensearch follows the same rules as kafka or pg (core plus OpenSearch-category tools); there are no OpenSearch-specific tools yet, so it currently exposes core only.
{
"mcpServers": {
"aiven-mcp": {
"url": "https://mcp.aiven.live/mcp?services_scope=kafka"
}
}
}
You can also combine with read_only:
https://mcp.aiven.live/mcp?services_scope=pg&read_only=true
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.
https://mcp.aiven.live/mcp?read_only=true&write_allowlist=aiven_kafka_topic_create
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 |
{
"mcpServers": {
"aiven-mcp": {
"url": "https://mcp.aiven.live/mcp/<marketplace>"
}
}
}
The path segment combines with the query parameters above, for example https://mcp.aiven.live/mcp/gcp?services_scope=pg&read_only=true.
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
claude mcp add --scope user aiven-mcp -e AIVEN_TOKEN=your-token-here -- npx -y mcp-aiven
Cursor, VS Code -- add to your MCP client config:
{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "your-token-here"
}
}
}
}
Config file locations:
.vscode/mcp.json in your workspaceRun a local build of the server (useful for development and testing):
pnpm install && pnpm generate:api-types && pnpm generate && pnpm build && AIVEN_TOKEN="<YOUR_TOKEN>" MCP_TRANSPORT="http" PORT=3000 node dist/index.js
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:
MCP_HOST=http://localhost:3000 node dist/index.js
| 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 |
AIVEN_SERVICES_SCOPE | No | -- | Comma-separated scopes to expose (e.g. kafka, pg,kafka, or all). Valid: all, core, pg, kafka, application, integrations, opensearch. core is included implicitly for scoped service types. opensearch has no dedicated tools yet (core only until OpenSearch tools are added). Omitting the var or setting all loads every tool. |
AIVEN_ALLOW_SECRETS | No | false | Set to true to expose the aiven_service_connection_info tool, which returns live credentials (passwords, connection URIs, certs) into the conversation. Disabled while AIVEN_READ_ONLY=true. |
AIVEN_WRITE_ALLOWLIST | No | -- | Comma-separated tool names to re-enable while AIVEN_READ_ONLY=true (e.g. aiven_kafka_topic_create). Ignored when read-only mode is not enabled. |
MCP_HOST | No | https://mcp.aiven.live | Override the OAuth protected resource host |
MCP_TRANSPORT | No | stdio | Set to http to start an HTTP server instead of stdio |
MCP_HTTP_RATE_LIMIT_MAX | No | 1000 | Max requests per window on POST /mcp (HTTP transport), per bearer token. Client IP rate limiting is expected at Cloudflare. |
MCP_HTTP_RATE_LIMIT_WINDOW_MS | No | 60000 | Window length in milliseconds for MCP_HTTP_RATE_LIMIT_MAX. |
EXTRA_PROTECTION | No | false | Set to true on HTTP deployments to require a valid X-Edge-Auth header on every request except GET /health. See Edge protection rollout below. |
MCP_EDGE_AUTH_SECRET | When EXTRA_PROTECTION=true | -- | Shared secret; must match the value Cloudflare injects as X-Edge-Auth via Transform Rules. |
In remote (HTTP) mode, AIVEN_TOKEN is not needed. Your MCP client sends your token as a Bearer token with each request.
Production HTTP traffic is rate-limited in two layers: Cloudflare enforces a per-client-IP limit (configured in the Cloudflare dashboard), and this server enforces MCP_HTTP_RATE_LIMIT_* per bearer token on POST /mcp.
When EXTRA_PROTECTION=true, any mismatch between MCP_EDGE_AUTH_SECRET and the value Cloudflare injects as X-Edge-Auth causes every request to return 403 (except GET /health). Both values are environment/config on opposite sides of the wire, so the only recovery path is to fix the secret and redeploy or update Cloudflare.
Enable in this order:
X-Edge-Auth (and, if used for PG tools, X-Client-IP) on traffic to the MCP origin. Note the secret value you configure.MCP_EDGE_AUTH_SECRET — Deploy the server with this env var set to the same secret as the Transform Rule. Leave EXTRA_PROTECTION unset or false for now; verify the origin still accepts traffic.EXTRA_PROTECTION=true — Enable only after steps 1–2 are live and matched. Confirm a normal MCP request succeeds and direct origin access without X-Edge-Auth is rejected.MCP_EDGE_AUTH_SECRET together (or briefly set EXTRA_PROTECTION=false), redeploy, then re-enable. Never rotate one side alone while the flag is on.If EXTRA_PROTECTION=true at startup and MCP_EDGE_AUTH_SECRET is missing, the process exits immediately with an error.
While rejections continue, the server logs a misconfig warning at most once every 15 minutes (reset after a request with valid X-Edge-Auth), so a secret mismatch is visible in logs without one line per rejected request.
Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.
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.
| Tool | Description |
|---|---|
aiven_project_list | List projects |
aiven_project_get | Get project details |
aiven_list_project_clouds | List cloud platforms for a project |
aiven_project_vpc_list | List VPCs for a project |
aiven_service_list | List services |
aiven_service_type_plans | List plans with cloud availability |
aiven_service_type_get | Get default and available engine versions for a service type |
aiven_service_plan_pricing | Get pricing for a plan in a specific cloud |
aiven_service_create | Create a service |
aiven_service_get | Get service information |
aiven_service_update | Update a service (plan, config, power state) |
aiven_service_metrics_fetch | Fetch metrics for managed data services |
aiven_service_application_metrics_get | Fetch metrics for application services |
aiven_project_get_service_logs | Get service log entries |
aiven_service_query_activity | Fetch current queries for a service |
aiven_project_get_event_logs | Get project event log entries |
| Tool | Description |
|---|---|
aiven_kafka_topic_list | List Kafka topics |
aiven_kafka_topic_create | Create a Kafka topic |
aiven_kafka_topic_get | Get Kafka topic info |
aiven_kafka_topic_update | Update a Kafka topic |
aiven_kafka_topic_delete | Delete a Kafka topic |
aiven_kafka_topic_message_list | Read messages from a Kafka topic |
aiven_kafka_topic_message_produce | Produce messages into a Kafka topic |
aiven_kafka_connect_available_connectors | List available connector types |
aiven_kafka_connect_list | List running connectors |
aiven_kafka_connect_create_connector | Create a connector |
aiven_kafka_connect_edit_connector | Edit a connector |
aiven_kafka_connect_get_connector_status | Get connector status |
aiven_kafka_connect_pause_connector | Pause a connector |
aiven_kafka_connect_resume_connector | Resume a connector |
aiven_kafka_connect_restart_connector | Restart a connector |
aiven_kafka_connect_delete_connector | Delete a connector |
aiven_kafka_schema_registry_subjects | List Schema Registry subjects |
aiven_kafka_schema_registry_subject_version_get | Get Schema Registry subject version |
| Tool | Description |
|---|---|
aiven_pg_service_available_extensions | List available extensions |
aiven_pg_service_query_statistics | Fetch query statistics |
aiven_pg_bouncer_create | Create a PgBouncer connection pool |
aiven_pg_bouncer_update | Update a PgBouncer connection pool |
aiven_pg_bouncer_delete | Delete a PgBouncer connection pool |
aiven_pg_read | Run a read-only SQL query |
aiven_pg_write | Run a write SQL statement (INSERT, UPDATE, DELETE, CREATE TABLE, etc.) |
aiven_pg_optimize_query | AI-powered query optimization (EverSQL) |
| Tool | Description |
|---|---|
aiven_application_create | Create and initially deploy a Containerfile/Dockerfile application; returns 409 if the service already exists |
aiven_application_redeploy | Rebuild an existing application from its configured repository without changing service configuration |
aiven_vcs_integration_initialize | Start the browser-based flow for connecting a GitHub account |
aiven_vcs_integration_list | List connected VCS (GitHub) accounts |
aiven_vcs_integration_repository_list | List repositories for a VCS integration |
aiven_vcs_integration_repository_branch_list | List repository branches and their current commit SHAs |
aiven_vcs_integration_repository_container_manifest_files_list | Find candidate Containerfile, Dockerfile, and Compose manifests |
aiven_vcs_integration_repository_scan_container_manifest | Derive candidate Aiven service configurations from a Containerfile, Dockerfile, or supported parts of a Compose file |
| Tool | Description |
|---|---|
aiven_docs_search | Search the official Aiven documentation in natural language. Only available on the hosted server (https://mcp.aiven.live/mcp) — not exposed in self-hosted deployments. |
See CONTRIBUTING.md for development setup, running locally, and adding new tools.