aiven_open_mcp_aiven.git
by Aiven-OpenAiven MCP Server: Model Context Protocol Integration for Aiven Services
Overview
The Aiven MCP Server is a specialized implementation of the Model Context Protocol (MCP) designed to integrate seamlessly with Aiven's ecosystem. It provides access to Aiven's managed services, including PostgreSQL, Kafka, ClickHouse, Valkey, and OpenSearch, enabling developers to build full-stack solutions powered by Large Language Models (LLMs).
Features
Tools
The Aiven MCP Server includes the following tools to interact with Aiven services:
- list_projects: Lists all projects on your Aiven account.
- list_services: Lists all services within a specific Aiven project.
- get_service_details: Retrieves detailed information about a specific service in an Aiven project.
Configuration for Claude Desktop
To configure the Aiven MCP Server for Claude Desktop, follow these steps:
1. Open the Claude Desktop configuration file:
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%/Claude/claude_desktop_config.json
2. Add the following configuration:
json
{
"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"
}
}
}
}
3. Update the environment variables:
- Replace $REPOSITORY_DIRECTORY with the path to the repository.
- Set AIVEN_TOKEN to your Aiven authentication token.
4. Locate the uv command entry and replace it with the absolute path to the uv executable.
5. Restart Claude Desktop to apply the changes.
Configuration for Cursor
To configure the Aiven MCP Server for Cursor:
1. Navigate to Cursor -> Settings -> Cursor Settings.
2. Select MCP Servers.
3. 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
4. Add AIVEN_BASE_URL, AIVEN_PROJECT_NAME, and AIVEN_TOKEN as variables.
Development
Setup
- Add the following variables to a
.envfile in the repository root:
AIVEN_BASE_URL=https://api.aiven.io AIVEN_TOKEN=$AIVEN_TOKEN - Install dependencies using
uv sync. Follow the uv installation instructions. - Activate the virtual environment:
source .venv/bin/activate. - Start the MCP server for testing:
mcp dev mcp_aiven/mcp_server.py.
Environment Variables
Required Variables
AIVEN_BASE_URL: The Aiven API URL.AIVEN_TOKEN: The Aiven authentication token.
Developer Considerations for MCPs and AI Agents
Self-Managed MCPs
- Customer Responsibility: MCPs run in the user's environment, not hosted by Aiven. Users are responsible for operational management, security, and compliance.
- Deployment and Maintenance: Developers handle all aspects of MCP deployment and updates.
AI Agent Security
- Permission Control: AI Agent capabilities are tied to the permissions of the API token.
- Credential Handling: Exercise caution when providing credentials to AI Agents.
- Risk Assessment: Conduct thorough risk assessments before granting access to sensitive resources.
API Token Best Practices
- Principle of Least Privilege: Restrict API tokens to the minimum necessary permissions.
- Token Management: Implement secure storage and regular rotation practices.
About
The Aiven MCP Server is an open-source project under the Apache-2.0 license. It provides a robust interface for integrating Aiven services with AI-driven workflows.
Invite Gmail Contacts
