Skip to main content

Aiven MCP Limited availability

note

The Aiven MCP server is in Limited availability. Request access when you first connect.

Create and manage Aiven services from AI assistants such as Cursor and Claude Code, including PostgreSQL®, Apache Kafka®, plans, metrics, logs, and service configuration. Enable read-only mode in the configuration tabs below to restrict the server to non-destructive operations.

Prerequisites

  • An Aiven account
  • An MCP-compatible client (Cursor, Claude Code, Claude Desktop, or VS Code)

Authentication uses OAuth 2.0 with PKCE; your browser opens on first connect so you can sign in and authorize MCP access.

Install the Aiven MCP

For one-click installation:

Add to Cursor

To add the server manually:

  1. In your project root, create or edit the .cursor/mcp.json file.
  2. Add the following configuration:

Allows only read-only operations, such as listing services, viewing metrics, and running read-only queries.

{
"mcpServers": {
"aiven": {
"type": "http",
"url": "https://mcp.aiven.live/mcp"
}
}
}
  1. Save the file.
  2. Restart Cursor.
  3. Open Settings > Tools & MCP.
  4. Select aiven and click Connect.

For more information, see the Cursor MCP documentation.


Verify the connection

  1. Open Cursor Chat with Cmd+L on macOS or Ctrl+L on Windows/Linux.

  2. Try a prompt such as:

    List my Aiven projects.

  3. If prompted to allow tool execution, click Allow.

  4. To confirm the server is registered, go to Settings > Tools & MCP and check that aiven appears with a connected status.

Security and responsibility

important

MCP tools can perform destructive operations on your Aiven services, including creating, modifying, and deleting services, databases, topics, and data.

AI agents run operations from natural language prompts, which can be misinterpreted. Using the Aiven MCP server can result in damage to or loss of data.

Decide whether to enable MCP access in your organization after evaluating the risks.

Under the shared responsibility model, security and compliance for MCP usage are shared between Aiven and your organization. Aiven secures the platform and API. You are responsible for the following:

  • Decide whether to enable MCP in your organization and evaluate the associated risks.
  • Control access by scoping API tokens to the minimum permissions needed (principle of least privilege) and rotating them regularly.
  • Review AI agent actions before they run, especially for write or delete operations on production resources.
  • Configure MCP servers securely, including enabling read-only mode to restrict the server to non-destructive operations.