de en es ja ko ru zh

Aiven MCP Server

Name: Aiven MCP Server
Author: Aiven-Open

Official

by Aiven-Open

Overview Schema Related Servers Score Discussions

TypeScript

Hybrid

Сервер MCP Aiven

Сервер протокола контекста модели (MCP) для Aiven.

Это обеспечивает доступ к сервисам Aiven для PostgreSQL, Kafka, ClickHouse, Valkey и OpenSearch, работающим в Aiven, и более широкой экосистеме собственных коннекторов Aiven. Позволяет LLM создавать полнофункциональные решения для всех вариантов использования.

Функции

Инструменты

list_projects
- Перечислите все проекты в вашей учетной записи Aiven.
list_services
- Перечислите все услуги в конкретном проекте Aiven.
get_service_details
- Получите подробную информацию о вашем услуге в конкретном проекте Aiven.

Related MCP server: MCP TapData Server

Конфигурация для Claude Desktop

Откройте файл конфигурации Claude Desktop, расположенный по адресу:
- В macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- В Windows: %APPDATA%/Claude/claude_desktop_config.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"
      }
    }
  }
}

Обновите переменные среды:

$REPOSITORY_DIRECTORY для указания на папку, содержащую репозиторий
AIVEN_TOKEN к токену входа Aiven .

Найдите запись команды для uv и замените ее абсолютным путем к исполняемому файлу uv . Это гарантирует, что при запуске сервера будет использоваться правильная версия uv . На Mac вы можете найти этот путь, используя which uv .
Перезапустите Claude Desktop, чтобы изменения вступили в силу.

Конфигурация для курсора

Перейдите в Курсор -> Настройки -> Настройки курсора.
Выберите «Серверы MCP»
Добавьте новый сервер с
- Имя: mcp-aiven
- Тип: command
- Команда: uv --directory $REPOSITORY_DIRECTORY run --with-editable $REPOSITORY_DIRECTORY --python 3.13 mcp-aiven

Где $REPOSITORY_DIRECTORY — это путь к репозиторию. Возможно, вам придется добавить AIVEN_BASE_URL , AIVEN_PROJECT_NAME и AIVEN_TOKEN в качестве переменных

Разработка

Добавьте следующие переменные в файл .env в корне репозитория.

AIVEN_BASE_URL=https://api.aiven.io
AIVEN_TOKEN=$AIVEN_TOKEN

Запустите uv sync для установки зависимостей. Для установки uv следуйте инструкциям здесь . Затем выполните source .venv/bin/activate .
Для простоты тестирования вы можете запустить mcp dev mcp_aiven/mcp_server.py чтобы запустить сервер MCP.

Переменные среды

Для настройки соединения Aiven используются следующие переменные среды:

Требуемые переменные

AIVEN_BASE_URL : URL-адрес API Aiven.
AIVEN_TOKEN : токен аутентификации.

Available Tools

3 tools

get_service_detailsD

ParametersJSON Schema

Name	Required	Description	Default
`project_name`	Yes
`service_name`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_projectsD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_servicesD

ParametersJSON Schema

Name	Required	Description	Default
`project_name`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

3 tool updatesv1.0.0Apr 10, 2025
- First observedget_service_details
- First observedlist_projects
- First observedlist_services

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.8/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: get_service_details retrieves specific service information, list_projects enumerates projects, and list_services enumerates services. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_service_details, list_projects, list_services) with clear, descriptive names. The naming convention is uniform throughout the set.

Tool Count2/5

With only 3 tools, the server feels under-scoped for managing Aiven services, which typically involve operations like create, update, delete, or configure services. The count is too low for comprehensive coverage of the domain.

Completeness2/5

The tool set is severely incomplete for a service management domain; it lacks essential CRUD operations (e.g., create_service, update_service, delete_service) and other key actions like managing configurations or monitoring, leaving significant gaps that will hinder agent workflows.

Maintenance

ActivityActive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp COAuth
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
216
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
Sentry AOAuth
dev.sentry.mcp
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Monitoring Developer Tools Observability
3
Apideck MCP A
dev.apideck.mcp
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Developer Tools
42

Related MCP Servers

ClickHouse MCP Server
Databases RAG Systems Code Execution
ThomAub
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables Large Language Models to seamlessly interact with ClickHouse databases, supporting resource listing, schema retrieval, and query execution.
Updated 2 years ago (2024-12-18 18:34 UTC)
2
MIT
MCP TapData Serverofficial
Databases Search Developer Tools
tapdata
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables Large Language Models to access and interact with database connections, including viewing schemas and performing CRUD operations on connected databases.
Updated a year ago (2025-05-11 23:02 UTC)
-
MCP Boilerplate
RAG Systems Agent Orchestration Developer Tools
iamsrikanthnani
A
license
Not graded
quality
D
maintenance
A server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.
Updated a year ago (2025-05-12 06:05 UTC)
15
11
MIT
RL-MCP
RAG Systems Agent Orchestration Databases
rlefko
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.
Updated a year ago (2025-05-31 18:35 UTC)
2
-

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aiven-Open/mcp-aiven'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Сервер MCP Aiven

Функции

Инструменты

Конфигурация для Claude Desktop

Конфигурация для курсора

Разработка

Переменные среды

Требуемые переменные

Рекомендации разработчикам по протоколам контекста модели (MCP) и агентам ИИ

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

ClickHouse MCP Server

MCP TapData Serverofficial

MCP Boilerplate

RL-MCP

Appeared in Searches

Latest Blog Posts

MCP directory API