de en es ja ko ru zh

Aiven MCP Server

Name: Aiven MCP Server
Author: Aiven-Open

Official

by Aiven-Open

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Hybrid

Aiven MCP 服务器

Aiven 的模型上下文协议(MCP) 服务器。

这允许访问在 Aiven 中运行的 Aiven for PostgreSQL、Kafka、ClickHouse、Valkey 和 OpenSearch 服务，以及更广泛的 Aiven 原生连接器生态系统。使 LLM 能够为所有用例构建全栈解决方案。

特征

工具

list_projects
- 列出您的 Aiven 帐户上的所有项目。
list_services
- 列出特定 Aiven 项目中的所有服务。
get_service_details
- 获取特定 Aiven 项目中服务的详细信息。

Related MCP server: MCP TapData Server

Claude 桌面配置

打开位于以下位置的 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 ：Aiven API url
AIVEN_TOKEN ：身份验证令牌

模型上下文协议 (MCP) 和 AI 代理的开发人员注意事项

本节概述了使用本系统内的模型上下文协议 (MCP) 和 AI 代理时，开发人员的主要职责和安全注意事项。自管理 MCP：

客户责任： MCP 在用户环境中运行，而非由 Aiven 托管。因此，用户应自行负责其运营管理、安全性和合规性，并遵循共担责任模式。( https://aiven.io/responsibility-matrix )
**部署和维护：**开发人员必须处理 MCP 部署、更新和维护的所有方面。

AI代理安全：

权限控制： AI 代理的访问和功能严格受用于身份验证的 API 令牌授予的权限控制。开发人员必须精心管理这些权限。
**凭证处理：**请谨慎注意，AI 代理可能需要访问凭证（例如，数据库连接字符串、流媒体服务令牌）才能代表您执行操作。向 AI 代理提供此类凭证时请务必谨慎。
**风险评估：**在授予 AI 代理访问敏感资源的权限之前，请遵守组织的安全政策并进行彻底的风险评估。

API 令牌最佳实践：

**最小权限原则：**始终遵循最小权限原则。API 令牌应限定其使用范围，并限制在其预期功能所需的最低权限范围内。
**令牌管理：**实施强大的令牌管理实践，包括定期轮换和安全存储。

关键要点：

用户对 MCP 的执行和安全拥有完全的控制权和责任。
AI 代理权限与 API 令牌权限直接相关。
向 AI 代理提供凭证时要格外小心。
管理 API 令牌时严格遵守最小特权原则。

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

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

ResponsivenessUnresponsive

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)
7
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

Aiven MCP 服务器

特征

工具

Claude 桌面配置

光标配置

发展

环境变量

必需变量

模型上下文协议 (MCP) 和 AI 代理的开发人员注意事项

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