Skip to main content

Aiven MCP Early availability

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, or limit tools to specific services to keep the assistant focused.

Prerequisites

  • An Aiven account
  • An MCP-compatible client, such as Cursor, Claude Code, Claude Desktop, VS Code, or Gemini CLI
  • MCP access enabled for your organization by an admin in the Aiven Console under Admin settings > Authentication > Allow MCP connection

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

  1. Open a terminal.

  2. Choose your options below, then run the generated command:

    claude mcp add --transport http aiven https://mcp.aiven.live/mcp?read_only=true
  3. To verify the server is registered, in Claude Code run /mcp. The first time you use the server, your browser opens.

  4. Sign in to Aiven and select your organization.

For more information, see the Claude Code MCP documentation.


Verify the connection

  1. Run /mcp in Claude Code to verify the server is registered.

  2. Try a prompt such as:

    List my Aiven projects.

  3. If your client prompts you to allow tool execution, approve the request.

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.

Aiven secures the MCP server and data in transit. Your selected AI agent provider determines how the agent uses your data, including whether it uses that data for training. Review the provider's terms before you enable the integration.

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.