YuniKorn MCP Server
A Model Context Protocol (MCP) server that interfaces with the Apache YuniKorn Scheduler, allowing AI agents to observe and reason about Kubernetes batch workload resource management, queue hierarchies, and application states.
README
YuniKorn MCP Server
A Model Context Protocol (MCP) server that interfaces with the Apache YuniKorn Scheduler, allowing AI agents to observe and reason about Kubernetes batch workload resource management, queue hierarchies, and application states.
Screenshots
Inspecting Yunikorn tools using MCP inspector

Querying the Yunikorn scheduler via MCP using Opencode

Features
- 7 MCP Tools: Query partitions, queues, applications, nodes, user usage, and scheduler health
- 2 MCP Resources: Static data access for partitions list and node utilization
- Async HTTP: Non-blocking API calls using
httpx - Proper Error Mapping: YuniKorn HTTP errors mapped to standard MCP error responses
- Resource Awareness: Handles YuniKorn's raw bytes and millicore values
- CORS Enabled: Allows connections from any origin for browser-based MCP Inspector
- Streamable HTTP: Default transport with stdio fallback for IDE integration
Installation
uv pip install -r requirements.txt
If you are using a virtual environment, make sure it is activated first:
source .venv/bin/activate
uv pip install -r requirements.txt
Usage
Running the Server
The default transport is Streamable HTTP on port 8000:
Run locally
uv run python -m main
Run with Docker
docker run -p 8000:8000 -e YUNIKORN_BASE_URL="http://<REPLACE_ME>/ws/v1" docker.io/frenoid/yunikorn-mcp-server:latest
Command line options
| Option | Description | Default |
|---|---|---|
--transport |
Transport protocol (stdio, streamable-http) |
streamable-http |
--host |
Host to bind (HTTP transport only) | 0.0.0.0 |
--port |
Port to listen on (HTTP transport only) | 8000 |
--log-level |
Logging level | INFO |
Examples:
# Streamable HTTP on custom port
uv run python -m main --transport streamable-http --host 127.0.0.1 --port 8080
# Stdio mode for Claude Code / IDE integration
uv run python -m main --transport stdio
Environment Variables
| Variable | Description | Default |
|---|---|---|
YUNIKORN_BASE_URL |
Base URL of the YuniKorn REST API | http://localhost:9089/ws/v1/ |
TLS_INSECURE |
Disable HTTPS certificate verification (true/false) |
false |
# Connect to a remote YuniKorn instance
YUNIKORN_BASE_URL=http://yunikorn.example.com:9089/ws/v1/ uv run python -m main
# Connect to an HTTPS endpoint with a self-signed certificate
YUNIKORN_BASE_URL=https://yunikorn.example.com:9089/ws/v1/ TLS_INSECURE=true uv run python -m main
Connecting with MCP Inspector
The Streamable HTTP endpoint is exposed at the /mcp path:
http://localhost:8000/mcp
Testing
Run the test suite against a live YuniKorn instance:
YUNIKORN_BASE_URL=http://your-yunikorn-host:9089/ws/v1/ uv run python test_server.py
To run a quick compliance check:
YUNIKORN_BASE_URL=http://your-yunikorn-host:9089/ws/v1/ uv run python test_updated_server.py
Data Format Notes
- Memory: Represented in raw bytes (64-bit signed integers).
- CPU (vcore): Represented in millicores (thousandths of a core, i.e. 1000m = 1 core).
- Other resources: No specific unit assigned.
- Active applications: The virtual "active" state represents New, Accepted, Running, Completing, and Failing statuses.
- allocationID vs uuid:
uuidis deprecated.allocationIDcontains the same base value asuuidwith a hyphen-counter suffix (e.g.,-0,-1). - allocationDelay: The difference between
allocationTimeandrequestTimefor an allocation.
API Conformance
This MCP server conforms to the Apache YuniKorn Scheduler REST API (v1.8.0). Each tool maps directly to a documented endpoint.
| Tool | YuniKorn Endpoint |
|---|---|
get_partitions |
GET /ws/v1/partitions |
get_partition_queues |
GET /ws/v1/partition/{partitionName}/queues |
get_applications_by_state |
GET /ws/v1/partition/{partitionName}/applications/{state}?status={status} |
inspect_application |
GET /ws/v1/partition/{partitionName}/application/{appId} |
get_node_details |
GET /ws/v1/partition/{partitionName}/nodes or /node/{nodeId} |
get_user_usage |
GET /ws/v1/partition/{partitionName}/usage/users or /usage/user/{userName} |
check_scheduler_health |
GET /ws/v1/scheduler/healthcheck |
Resources:
| Resource | YuniKorn Endpoint |
|---|---|
yunikorn://partitions/list |
GET /ws/v1/partitions |
yunikorn://nodes/utilization |
GET /ws/v1/scheduler/node-utilizations |
Error Mapping
| YuniKorn HTTP Code | MCP Error |
|---|---|
400 Bad Request |
INVALID_REQUEST |
404 Not Found |
INVALID_REQUEST |
500 Internal Server Error |
INTERNAL_ERROR |
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。