A
licenseNot graded
qualityD
maintenanceA Model Context Protocol server that enables Large Language Models to seamlessly interact with ClickHouse databases, supporting resource listing, schema retrieval, and query execution.
2
MIT
Aiven MCP Server
Officialby Aiven-Open
Aiven MCP 서버
Aiven을 위한 MCP( Model Context Protocol ) 서버.
이를 통해 Aiven에서 실행되는 PostgreSQL, Kafka, ClickHouse, Valkey 및 OpenSearch 서비스 및 더 광범위한 Aiven 네이티브 커넥터 생태계에 대한 Aiven for PostgreSQL, Kafka, ClickHouse, Valkey 및 OpenSearch 서비스에 액세스할 수 있습니다. LLM은 이를 통해 모든 사용 사례에 대한 풀스택 솔루션을 구축할 수 있습니다.
특징
도구
list_projectsAiven 계정의 모든 프로젝트를 나열하세요.
list_services특정 Aiven 프로젝트의 모든 서비스를 나열합니다.
get_service_detailsAiven 프로젝트의 특정 서비스에 대한 세부 정보를 얻으세요.
Related MCP server: MCP TapData Server
Claude Desktop 구성
다음 위치에 있는 Claude Desktop 구성 파일을 엽니다.
macOS의 경우:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows의 경우:
%APPDATA%/Claude/claude_desktop_config.json
다음을 추가합니다.
지엑스피1
환경 변수를 업데이트합니다.
$REPOSITORY_DIRECTORY저장소를 포함하는 폴더를 가리킵니다.AIVEN_TOKENAiven 로그인 토큰 으로 변경합니다.
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_TOKENuv sync실행하여 종속성을 설치하세요.uv설치하려면 여기의 지침을 따르세요. 그런 다음source .venv/bin/activate실행하세요.간편하게 테스트하려면
mcp dev mcp_aiven/mcp_server.py실행하여 MCP 서버를 시작할 수 있습니다.
환경 변수
다음 환경 변수는 Aiven 연결을 구성하는 데 사용됩니다.
필수 변수
AIVEN_BASE_URL: Aiven API URLAIVEN_TOKEN: 인증 토큰
모델 컨텍스트 프로토콜(MCP) 및 AI 에이전트에 대한 개발자 고려 사항
이 섹션에서는 이 시스템 내에서 모델 컨텍스트 프로토콜(MCP) 및 AI 에이전트를 사용할 때 개발자의 주요 책임과 보안 고려 사항을 간략하게 설명합니다. 자체 관리형 MCP:
고객 책임: MCP는 Aiven에서 호스팅하는 것이 아니라 사용자 환경에서 실행됩니다. 따라서 사용자는 공유 책임 모델을 준수하여 운영 관리, 보안 및 규정 준수에 대한 전적인 책임을 집니다. ( https://aiven.io/responsibility-matrix )
배포 및 유지관리: 개발자는 MCP 배포, 업데이트 및 유지관리의 모든 측면을 처리해야 합니다.
AI 에이전트 보안:
권한 제어: AI 에이전트의 접근 및 기능은 인증에 사용되는 API 토큰에 부여된 권한에 따라 엄격하게 관리됩니다. 개발자는 이러한 권한을 세심하게 관리해야 합니다.
자격 증명 처리: AI Agent가 사용자를 대신하여 작업을 수행하기 위해 액세스 자격 증명(예: 데이터베이스 연결 문자열, 스트리밍 서비스 토큰)을 요구할 수 있다는 점에 유의하십시오. AI Agent에 이러한 자격 증명을 제공할 때는 각별히 주의하십시오.
위험 평가: 조직의 보안 정책을 준수하고 AI 에이전트에게 중요한 리소스에 대한 액세스 권한을 부여하기 전에 철저한 위험 평가를 실시하세요.
API 토큰 모범 사례:
최소 권한 원칙: 항상 최소 권한 원칙을 준수하십시오. API 토큰은 의도된 기능에 필요한 최소한의 권한으로 범위를 지정하고 제한해야 합니다.
토큰 관리: 정기적인 순환 및 안전한 보관을 포함한 강력한 토큰 관리 관행을 구현합니다.
주요 내용:
사용자는 MCP 실행 및 보안에 대한 전적인 통제권과 책임을 갖습니다.
AI 에이전트 권한은 API 토큰 권한과 직접적으로 연결됩니다.
AI 에이전트에게 자격 증명을 제공할 때는 각별히 주의하세요.
API 토큰을 관리할 때는 최소 권한 원칙을 엄격히 준수하세요.
Available Tools
3 toolsget_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 updates
v1.0.0- First observed
get_service_details - First observed
list_projects - First observed
list_services
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
ResponsivenessUnresponsive
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
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
Related MCP Servers
MCP TapData Serverofficial
FlicenseNot gradedqualityDmaintenanceA 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.-- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.711MIT
- FlicenseNot gradedqualityDmaintenanceA 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.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 .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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