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

Aiven MCP サーバー

Aiven 用のモデルコンテキストプロトコル(MCP) サーバー。

これにより、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デスクトップの設定

次の場所にある 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変数として追加する必要AIVEN_BASE_URLあるかもしれません。

発達

リポジトリのルートにある.envファイルに次の変数を追加します。

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

uv syncを実行して依存関係をインストールします。uvをインストールするには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