Aiven MCP Limited 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
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
- Cursor
- Claude Code
- Claude Desktop
- VS Code
- Gemini CLI
- Other clients
- Local installation
For one-click installation:
Add to CursorTo add the server manually:
- In your project root, create or edit the
.cursor/mcp.jsonfile. - Choose your options below, then copy the generated configuration into the file:
{
"mcpServers": {
"aiven": {
"type": "http",
"url": "https://mcp.aiven.live/mcp?read_only=true"
}
}
}
- Save the file.
- Restart Cursor.
- Open Settings > Tools & MCP.
- Select aiven and click Connect.
For more information, see the Cursor MCP documentation.
Verify the connection
-
Open Cursor Chat with Cmd+L on macOS or Ctrl+L on Windows/Linux.
-
Try a prompt such as:
List my Aiven projects.
-
If prompted to allow tool execution, click Allow.
-
To confirm the server is registered, go to Settings > Tools & MCP and check that aiven appears with a connected status.
-
Open a terminal.
-
Choose your options below, then run the generated command:
PermissionsAvailable toolsclaude mcp add --transport http aiven https://mcp.aiven.live/mcp?read_only=true -
To verify the server is registered, in Claude Code run
/mcp. The first time you use the server, your browser opens. -
Sign in to Aiven and select your organization.
For more information, see the Claude Code MCP documentation.
Verify the connection
-
Run
/mcpin Claude Code to verify the server is registered. -
Try a prompt such as:
List my Aiven projects.
-
If your client prompts you to allow tool execution, approve the request.
-
Open the Claude Desktop configuration file. If it does not exist, create it:
-
macOS:
~/Library/Application Support/Claude/claude_desktop_config.json -
Windows:
%APPDATA%\Claude\claude_desktop_config.json
-
-
Choose your options below, then add the generated configuration to the file:
PermissionsAvailable tools{
"mcpServers": {
"aiven": {
"type": "http",
"url": "https://mcp.aiven.live/mcp?read_only=true"
}
}
} -
Save the file and restart Claude Desktop.
For more information, see the Claude Desktop MCP documentation.
Verify the connection
-
Open a new conversation.
-
Verify that the MCP tools icon appears in the input area.
-
Try a prompt such as:
List my Aiven projects.
-
If prompted to allow tool execution, click Allow.
Requires VS Code 1.102 or later with the GitHub Copilot extension installed and enabled.
-
Open your workspace in VS Code.
-
In the workspace root, create a
.vscodedirectory. -
In the
.vscodedirectory, create or edit themcp.jsonfile. -
Choose your options below, then add the generated configuration to the file:
PermissionsAvailable tools{
"servers": {
"aiven": {
"type": "http",
"url": "https://mcp.aiven.live/mcp?read_only=true"
}
}
} -
Save the file.
-
Reload VS Code.
-
Open the Command Palette and run MCP: List Servers.
-
Confirm that aiven appears in the list.
For more information, see the VS Code MCP documentation.
Verify the connection
-
Open Copilot Chat in VS Code.
-
Open the Command Palette and run MCP: List Servers.
-
Confirm that aiven appears in the list.
-
Try a prompt such as:
List my Aiven projects.
-
If prompted to allow tool execution, click Allow.
-
Create or edit the
~/.gemini/settings.jsonfile. -
Add the following configuration:
PermissionsAvailable tools{
"mcpServers": {
"aiven": {
"httpUrl": "https://mcp.aiven.live/mcp?read_only=true"
}
}
} -
Save the file.
-
Run
geminito start the CLI. -
Run
/mcp auth aivento sign in via your browser. -
Run
/mcp listto confirm the server is connected.
Verify the connection
-
In the Gemini CLI, try a prompt such as:
List my Aiven projects.
-
If prompted to allow tool execution, approve the request.
-
Open your MCP client configuration.
-
Choose your options below, then add the generated configuration to your client:
PermissionsAvailable tools{
"mcpServers": {
"aiven": {
"url": "https://mcp.aiven.live/mcp?read_only=true"
}
}
}Most clients use a configuration similar to the above.
-
Save the file and restart your client.
Some clients require a transport type, such as "type": "http". If the configuration
fails, see your client documentation.
Verify the connection
-
Open your AI assistant.
-
Try a prompt such as:
List my Aiven projects.
-
If your client prompts you to allow tool execution, approve the request.
Run the server locally using npx instead of the hosted server. Requires
an Aiven API token. Set
AIVEN_READ_ONLY="true" to enable read-only mode.
- Cursor
- Claude Code
- Claude Desktop
- VS Code
- Other clients
-
In your project root, create or edit the
.cursor/mcp.jsonfile. -
Add the following configuration, replacing
your-token-herewith your Aiven API token:{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "your-token-here",
"AIVEN_READ_ONLY": "false"
}
}
}
} -
Save the file and restart Cursor.
-
Open a terminal.
-
Run the following command, replacing
your-token-herewith your Aiven API token:claude mcp add --scope user aiven-mcp -e AIVEN_TOKEN=your-token-here -e AIVEN_READ_ONLY=false -- npx -y mcp-aiven -
Run
/mcpin Claude Code to verify the server is registered.
-
Open the Claude Desktop configuration file.
-
Add the following configuration, replacing
your-token-herewith your Aiven API token:{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "your-token-here",
"AIVEN_READ_ONLY": "false"
}
}
}
} -
Save the file and restart Claude Desktop.
-
In the
.vscodedirectory, create or edit themcp.jsonfile. -
Add the following configuration, replacing
your-token-herewith your Aiven API token:{
"servers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "your-token-here",
"AIVEN_READ_ONLY": "false"
}
}
}
} -
Save the file and reload VS Code.
-
Open your MCP client configuration.
-
Add the following configuration, replacing
your-token-herewith your Aiven API token:{
"mcpServers": {
"aiven-mcp": {
"command": "npx",
"args": ["-y", "mcp-aiven"],
"env": {
"AIVEN_TOKEN": "your-token-here"
}
}
}
} -
Save the file and restart your client.
Security and responsibility
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.