Aiven MCP Server
Model Context Protocol server enabling LLMs to access and manage Aiven cloud data services.
Key Features
Use Cases
README
Aiven MCP Server
A Model Context Protocol (MCP) server for Aiven.
This provides access to the Aiven for PostgreSQL, Kafka, ClickHouse, Valkey and OpenSearch services running in Aiven and the wider Aiven ecosystem of native connectors. Enabling LLMs to build full stack solutions for all use-cases.
Features
Tools
-
list_projects- List all projects on your Aiven account.
-
list_services- List all services in a specific Aiven project.
-
get_service_details- Get the detail of your service in a specific Aiven project.
Configuration for Claude Desktop
-
Open the Claude Desktop configuration file located at:
- On macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - On Windows:
%APPDATA%/Claude/claude_desktop_config.json
- On macOS:
-
Add the following:
{
"mcpServers": {
"mcp-aiven": {
"command": "uv",
"args": [
"--directory",
"$REPOSITORY_DIRECTORY",
"run",
"--with-editable",
"$REPOSITORY_DIRECTORY",
"--python",
"3.13",
"mcp-aiven"
],
"env": {
"AIVEN_BASE_URL": "https://api.aiven.io",
"AIVEN_TOKEN": "$AIVEN_TOKEN"
}
}
}
}
Update the environment variables:
$REPOSITORY_DIRECTORYto point to the folder cointaining the repositoryAIVEN_TOKENto the Aiven login token.
-
Locate the command entry for
uvand replace it with the absolute path to theuvexecutable. This ensures that the correct version ofuvis used when starting the server. On a mac, you can find this path usingwhich uv. -
Restart Claude Desktop to apply the changes.
Configuration for Cursor
-
Navigate to Cursor -> Settings -> Cursor Settings
-
Select "MCP Servers"
-
Add a new server with
- Name:
mcp-aiven - Type:
command - Command:
uv --directory $REPOSITORY_DIRECTORY run --with-editable $REPOSITORY_DIRECTORY --python 3.13 mcp-aiven
- Name:
Where $REPOSITORY_DIRECTORY is the path to the repository. You might need to add the AIVEN_BASE_URL, AIVEN_PROJECT_NAME and AIVEN_TOKEN as variables
Development
- Add the following variables to a
.envfile in the root of the repository.
AIVEN_BASE_URL=https://api.aiven.io
AIVEN_TOKEN=$AIVEN_TOKEN
-
Run
uv syncto install the dependencies. To installuvfollow the instructions here. Then dosource .venv/bin/activate. -
For easy testing, you can run
mcp dev mcp_aiven/mcp_server.pyto start the MCP server.
Environment Variables
The following environment variables are used to configure the Aiven connection:
Required Variables
AIVEN_BASE_URL: The Aiven API urlAIVEN_TOKEN: The authentication token
Developer Considerations for Model Context Protocols (MCPs) and AI Agents
This section outlines key developer responsibilities and security considerations when working with Model Context Protocols (MCPs) and AI Agents within this system. Self-Managed MCPs:
- Customer Responsibility: MCPs are executed within the user's environment, not hosted by Aiven. Therefore, users are solely responsible for their operational management, security, and compliance, adhering to the shared responsibility model. (https://aiven.io/responsibility-matrix)
- Deployment and Maintenance: Developers must handle all aspects of MCP deployment, updates, and maintenance.
AI Agent Security:
- Permission Control: Access and capabilities of AI Agents are strictly governed by the permissions granted to the API token used for their authentication. Developers must meticulously manage these permissions.
- Credential Handling: Be acutely aware that AI Agents may require access credentials (e.g., database connection strings, streaming service tokens) to perform actions on your behalf. Exercise extreme caution when providing such credentials to AI Agents.
- Risk Assessment: Adhere to your organization's security policies and conduct thorough risk assessments before granting AI Agents access to sensitive resources.
API Token Best Practices:
- Principle of Least Privilege: Always adhere to the principle of least privilege. API tokens should be scoped and restricted to the minimum permissions necessary for their intended function.
- Token Management: Implement robust token management practices, including regular rotation and secure storage.
Key Takeaways:
- Users retain full control and responsibility for MCP execution and security.
- AI Agent permissions are directly tied to API token permissions.
- Exercise extreme caution when providing credentials to AI Agents.
- Strictly adhere to the principle of least privilege when managing API tokens.
Star History
Repository Owner
Organization
Repository Details
Programming Languages
Tags
Join Our Newsletter
Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.
Related MCPs
Discover similar Model Context Protocol servers
mcp-confluent
MCP server for managing Confluent Cloud resources via natural language.
mcp-confluent is a Model Context Protocol (MCP) server implementation designed to enable natural language interaction with Confluent Cloud REST APIs. It integrates with AI tools such as Claude Desktop and Goose CLI, allowing users to manage Kafka topics, connectors, and Flink SQL statements conversationally. The project offers flexible configuration, CLI usage, and supports various transports for secure and customizable operations.
- ⭐ 115
- MCP
- confluentinc/mcp-confluent
Multi-Database MCP Server (by Legion AI)
Unified multi-database access and AI interaction server with MCP integration.
Multi-Database MCP Server enables seamless access and querying of diverse databases via a unified API, with native support for the Model Context Protocol (MCP). It supports popular databases such as PostgreSQL, MySQL, SQL Server, and more, and is built for integration with AI assistants and agents. Leveraging the MCP Python SDK, it exposes databases as resources, tools, and prompts for intelligent, context-aware interactions, while delivering zero-configuration schema discovery and secure credential management.
- ⭐ 76
- MCP
- TheRaLabs/legion-mcp
CipherTrust Manager MCP Server
Enables AI assistants to access CipherTrust Manager securely via the Model Context Protocol.
CipherTrust Manager MCP Server provides an implementation of the Model Context Protocol (MCP), offering AI assistants such as Claude and Cursor a unified interface to interact with CipherTrust Manager resources. Communication is facilitated through JSON-RPC over stdin/stdout, enabling key management, CTE client management, user management, and connection management functionalities. The tool is configurable via environment variables and integrates with existing CipherTrust Manager instances using the ksctl CLI for secure resource access.
- ⭐ 7
- MCP
- sanyambassi/ciphertrust-manager-mcp-server
Klavis
One MCP server for AI agents to handle thousands of tools.
Klavis provides an MCP (Model Context Protocol) server with over 100 prebuilt integrations for AI agents, enabling seamless connectivity with various tools and services. It offers both cloud-hosted and self-hosted deployment options and includes out-of-the-box OAuth support for secure authentication. Klavis is designed to act as an intelligent connector, streamlining workflow automation and enhancing agent capability through standardized context management.
- ⭐ 5,447
- MCP
- Klavis-AI/klavis
Kanboard MCP Server
MCP server for seamless AI integration with Kanboard project management.
Kanboard MCP Server is a Go-based server implementing the Model Context Protocol (MCP) for integrating AI assistants with the Kanboard project management system. It enables users to manage projects, tasks, users, and workflows in Kanboard directly via natural language commands through compatible AI tools. With built-in support for secure authentication and high performance, it facilitates streamlined project operations between Kanboard and AI-powered clients like Cursor or Claude Desktop. The server is configurable and designed for compatibility with MCP standards.
- ⭐ 15
- MCP
- bivex/kanboard-mcp
Multi Database MCP Server
A unified server for structured, multi-database access via the Model Context Protocol.
Multi Database MCP Server provides a standardized interface for AI assistants to access and manage multiple databases concurrently through the Model Context Protocol. It supports automatic tool generation for SQL queries, transactions, schema exploration, and performance analysis for each connected database. Built using Clean Architecture, it is fully compatible with OpenAI Agents SDK, enabling seamless integration. The platform simplifies configuration and interaction with MySQL and PostgreSQL databases in a robust, modular environment.
- ⭐ 304
- MCP
- FreePeak/db-mcp-server
Didn't find tool you were looking for?