Skip to main content

Aiven MCP

Create and manage Aiven services from AI assistants such as Cursor and Claude Code, including PostgreSQL®, Apache Kafka®, plans, metrics, logs, and service configuration. Use read-only mode to limit MCP tools to viewing services and other resources. You can enable it in your client or as an organization policy. You can also 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 organization admin. In the Aiven Console, click Admin > Authentication > Allow MCP connections.

Authentication uses OAuth 2.0 with PKCE. When you authenticate a client for the first time, your browser opens so you can sign in and authorize MCP access. This is usually a one-time setup step per client.

note

Aiven owns the aiven.live domain and operates the hosted MCP server at mcp.aiven.live. The server uses the Aiven API at api.aiven.io for authorization.

Install the Aiven MCP

  1. Open a terminal.

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

    Read and write. The assistant can create, modify, and delete.

    Advanced settings

    Select your marketplace only if you subscribed to Aiven through AWS, Azure, or Google Cloud Marketplace. This helps you sign in to the correct console.

    claude mcp add --transport http aiven "https://mcp.aiven.live/mcp"
  3. Run claude to start Claude Code.

  4. Run /mcp, select aiven, and authenticate in your browser when prompted.

  5. Test the connection with a prompt such as List my Aiven projects. and approve the tool execution if prompted.

For more information, see the Claude Code MCP documentation.

What Aiven MCP can do

After you connect to Aiven MCP, you can work with Aiven resources in natural language. For example, you can do the following:

  • View resources: List projects, services, and integrations, or check the status, plan, and cloud region of a service.
  • Manage services: Create, update, and delete services such as PostgreSQL® and Apache Kafka®. You can also change service plans and configuration. Read-only mode restricts MCP tools to read-only operations, such as viewing services and other resources.
  • Inspect and troubleshoot services: View service metrics, logs, and configuration to investigate issues.
  • Use Aiven documentation: Ask questions and get answers based on the Aiven documentation.

Read-only mode

Read-only mode restricts MCP tools to viewing services and other resources. You cannot create, modify, or delete resources. Read-only mode applies at the organization level and the client level.

Organization level

Organization admins can restrict MCP connections to read-only operations for all users in the organization.

  1. In the organization, click Admin > Authentication.
  2. Select Restrict MCP connections to read-only operations.

Users cannot override this setting in their client configuration. Write operations fail even if a user configures their client without read-only mode.

For more information, see Set authentication policies for organization users.

Client level

You can enable read-only mode for your client in the installation configuration. The setting applies only to that client and does not change the organization policy. It cannot override an organization-level restriction.

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.

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 on MCP access. Evaluate whether to enable MCP in your organization and the associated risks.
  • Control access. Scope API tokens to the minimum permissions needed and rotate them regularly.
  • Review AI agent actions. Review actions before they run, especially write or delete operations on production resources.
  • Limit write access. Use read-only mode at the organization level for all users, or at the client level for an individual client.
  • Keep credentials off in production. The Allow connection credentials option (allow_secrets=true) returns PostgreSQL and Kafka connection credentials, including URIs, passwords, and certificates, to the AI agent. Use it only for development with non-production services that do not hold sensitive data.

The Aiven MCP server can also connect directly to PostgreSQL services running in a private VPC.