# How to connect the Aiven MCP server To connect the official Aiven MCP server, follow Aiven's setup instructions, then sign in with OAuth when your client prompts you. Add https://mcp.aiven.live/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"), with your chosen options as URL parameters. Aiven's install page generates the configuration for Claude Code, Cursor (including a one-click install), VS Code 1.102 or later with GitHub Copilot, Gemini CLI and other clients. For Claude Desktop, Aiven's configuration goes through the mcp-remote bridge. Keep connection credentials off for production: with them on, the agent receives PostgreSQL and Kafka URIs, passwords and certificates. If you can't use OAuth, run Aiven MCP locally with an API token. Aiven documents setup for Claude Code, Cursor, Claude and VS Code. - Registry endpoint (not ready to use as-is): https://mcp.aiven.live/mcp?read_only={read_only}&services_scope={services_scope}&allow_secrets={allow_secrets} - Transport: Streamable HTTP - Registry: io.aiven/mcp 1.18.1 - Publisher documentation reviewed: 2026-11-05 (not a tested connection) - Guide page: https://apitracker.io/mcp-guides/aiven-mcp ## Before you start - An Aiven account. Aiven MCP is included with the account at no extra cost. - MCP connections must be enabled for your organization. An organization admin turns them on in the Aiven Console under Admin, Authentication, Allow MCP connections. If you created the Aiven account, you are the admin. - Organization admins can restrict MCP connections to read-only operations. That policy overrides the client's read-only setting, so write tools fail even if you connect without read-only mode. - If you subscribed to Aiven through AWS, Azure or Google Cloud Marketplace, choose that marketplace in Aiven's install options so you sign in to the correct console. ## Steps 1. **Open Aiven's MCP install instructions for your client** 2. **Choose whether to expose only read-only tools** 3. **Choose which service tools to load (all, or PostgreSQL, Kafka or integrations)** 4. **Choose whether to allow connection credentials (development only)** 5. **Add the Aiven MCP server to your client** Add https://mcp.aiven.live/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"), with your chosen options as URL parameters. Aiven's install page generates the configuration for Claude Code, Cursor (including a one-click install), VS Code 1.102 or later with GitHub Copilot, Gemini CLI and other clients. For Claude Desktop, Aiven's configuration goes through the mcp-remote bridge. Keep connection credentials off for production: with them on, the agent receives PostgreSQL and Kafka URIs, passwords and certificates. 6. **Sign in to Aiven in your browser and authorize MCP access** 7. **If you can't use OAuth, run Aiven MCP locally with an API token** In headless environments or other cases where OAuth isn't possible, Aiven documents running its MCP server locally from the mcp-aiven npm package instead of the hosted server. It reads your Aiven API token from the AIVEN_TOKEN environment variable, and AIVEN_READ_ONLY and AIVEN_ALLOW_SECRETS set the same options. The token's permissions apply, so scope it to the minimum needed and rotate it regularly. This is a separate connection from the hosted server this guide covers. 8. **List the server's tools** ## Questions ### What is the Aiven MCP server URL? Aiven's MCP Registry record lists https://mcp.aiven.live/mcp?read_only={read_only}&services_scope={services_scope}&allow_secrets={allow_secrets} (Streamable HTTP), but that address isn't ready to use as-is. Add https://mcp.aiven.live/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"), with your chosen options as URL parameters. Aiven's install page generates the configuration for Claude Code, Cursor (including a one-click install), VS Code 1.102 or later with GitHub Copilot, Gemini CLI and other clients. For Claude Desktop, Aiven's configuration goes through the mcp-remote bridge. Keep connection credentials off for production: with them on, the agent receives PostgreSQL and Kafka URIs, passwords and certificates. ### How do I authenticate with the Aiven MCP server? Sign in with OAuth when your client prompts you. If you can't use OAuth, run Aiven MCP locally with an API token: In headless environments or other cases where OAuth isn't possible, Aiven documents running its MCP server locally from the mcp-aiven npm package instead of the hosted server. It reads your Aiven API token from the AIVEN_TOKEN environment variable, and AIVEN_READ_ONLY and AIVEN_ALLOW_SECRETS set the same options. The token's permissions apply, so scope it to the minimum needed and rotate it regularly. This is a separate connection from the hosted server this guide covers. ### Which AI clients can use the Aiven MCP server? Aiven's documentation covers Claude Code, Cursor, Claude and VS Code. Other clients that support remote Streamable HTTP MCP servers may also work. ### What do I need before connecting Aiven MCP? An Aiven account. Aiven MCP is included with the account at no extra cost. MCP connections must be enabled for your organization. An organization admin turns them on in the Aiven Console under Admin, Authentication, Allow MCP connections. If you created the Aiven account, you are the admin. Organization admins can restrict MCP connections to read-only operations. That policy overrides the client's read-only setting, so write tools fail even if you connect without read-only mode. If you subscribed to Aiven through AWS, Azure or Google Cloud Marketplace, choose that marketplace in Aiven's install options so you sign in to the correct console. ### Has this Aiven MCP guide been tested? Aiven's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work. ## Sources - https://aiven.io/docs/tools/mcp-server (checked 2026-11-05) - https://registry.modelcontextprotocol.io/v0.1/servers/io.aiven%2Fmcp/versions/1.18.1 (checked 2026-11-05) - https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization (checked 2026-11-05) Guide JSON: https://github.com/apideck-libraries/mcp-connect/blob/626f6a146170ded34891b30dca3af26f09e07466/proposals/connection-guide/0.1/reviewed/guides/aiven-mcp.json