Kubeflow MCP Server
Allows management of Kubeflow training jobs on Kubernetes clusters, including submitting fine-tuning and custom training jobs, monitoring logs and events, and managing job lifecycle through natural language.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kubeflow MCP ServerList all running training jobs in my cluster"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kubeflow MCP Server
AI-powered interface for Kubeflow Training via Model Context Protocol (MCP). Enable your AI assistants to manage distributed training jobs, fine-tune LLMs, and monitor workloads on Kubernetes — all through natural language.
Note: This project is in early development. APIs may change between versions.

Table of Contents
Related MCP server: k8s-mcp-server
Overview
The Kubeflow MCP Server bridges AI assistants/agents with Kubeflow's training infrastructure. Instead of writing YAML manifests or learning Kubernetes APIs, simply describe what you want to train and let AI handle the complexity.
Key Benefits
Natural Language Interface: Describe training jobs in plain English — "fine-tune Llama-3 on my dataset with 4 GPUs"
Smart Resource Planning: AI estimates GPU/memory requirements before job submission
Real-time Monitoring: Stream logs, track progress, and debug failures conversationally
Safe by Design: Preview configurations before submission, built-in validation and guardrails
Multi-Client Support: Works with Claude Desktop, Cursor IDE, MCP Inspector, or custom agents
Compatibility
Component | Version | Notes |
Kubeflow SDK | ≥0.4.0 | TrainerClient API for training jobs |
Kubernetes | ≥1.28 | With TrainJob CRD installed |
Python | ≥3.10 | Async support required |
This MCP server wraps the Kubeflow Training SDK TrainerClient API. All training operations (fine-tuning, custom scripts, container jobs) use SDK types like BuiltinTrainer, CustomTrainer, TorchTuneConfig, and LoraConfig.
Quick Start
Installation
pip install kubeflow-mcpConfiguration
Add to your MCP client configuration:
{
"mcpServers": {
"kubeflow": {
"command": "kubeflow-mcp",
"args": ["serve", "--persona", "ml-engineer"]
}
}
}Option | Values | Default |
|
|
|
|
|
|
|
|
|
Client | Config Path |
Cursor IDE |
|
Claude Desktop (macOS) |
|
Claude Desktop (Windows) |
|
{
"mcpServers": {
"kubeflow": {
"command": "podman",
"args": [
"run", "--rm", "-i",
"-v", "${HOME}/.kube:/home/mcp/.kube:ro",
"ghcr.io/kubeflow/mcp-server:latest",
"serve"
]
}
}
}Replace podman with docker if needed.
npx @modelcontextprotocol/inspector uv run kubeflow-mcp serveTry It
"What training jobs are running in my cluster?"
"Fine-tune google/gemma-2b on squad dataset with 2 GPUs"
"Show me logs for the failed training job"Tools
Category | Tools | Description |
Planning |
| Check capacity, estimate requirements |
Training |
| Submit training jobs |
Discovery |
| Browse jobs and runtimes |
Monitoring |
| Logs, events, status |
Lifecycle |
| Manage job lifecycle |
fine_tune(
model="google/gemma-2b",
dataset="squad",
num_nodes=2,
gpu_per_node=1,
confirmed=True
)Ask: "How much GPU memory do I need for Llama-3-70B?"
{
"model": "meta-llama/Llama-3-70B",
"parameters": "70B",
"estimated_memory_gb": 140,
"recommended_gpus": 4,
"gpu_type": "A100-80GB"
}Prompts
MCP prompts provide structured guidance for common workflows. MCP clients can discover and use these prompts:
Prompt | Description |
| Step-by-step guide for fine-tuning LLMs with LoRA |
| Guide for custom scripts or container training |
| Diagnose and fix common job failures |
| Plan resources before training |
| Monitor jobs and debug issues |
MCP clients that support prompts (like Claude Desktop) can list and invoke these prompts directly. The prompts provide detailed, parameterized guidance that helps ensure successful training operations.
Example with parameters:
fine_tuning_workflow(model="meta-llama/Llama-3.2-3B", dataset="tatsu-lab/alpaca")Resources
MCP resources provide read-only reference data that clients can fetch without consuming tool calls:
Resource URI | Content |
| Tested model configurations with GPU requirements |
| Runtime documentation and patches |
| Quick start guide for new users |
| Troubleshooting quick reference |
CLI
# Server
kubeflow-mcp serve # Start MCP server
kubeflow-mcp serve --clients trainer # Specify client
kubeflow-mcp serve --persona ml-engineer # Set persona
kubeflow-mcp status # Show server status
# Agent
kubeflow-mcp agent --backend ollama --model qwen3:8b
kubeflow-mcp agent --backend ollama --mode progressive
kubeflow-mcp agent --backend ollama --thinking # Enable thinking outputLocal Agent
Run a fully local AI agent with Ollama — no cloud APIs required:
pip install kubeflow-mcp[agents]
ollama pull qwen3:8b
kubeflow-mcp agent --backend ollama --model qwen3:8b
Mode | Description |
| All tools via MCP protocol (default) |
| 3 meta-tools for hierarchical discovery |
| 2 meta-tools with embedding-based search |
kubeflow-mcp agent --backend ollama # Full mode (default)
kubeflow-mcp agent --backend ollama --mode progressive # Hierarchical discovery
kubeflow-mcp agent --backend ollama --mode semantic # requires sentence-transformersFull mode connects via the standard MCP stdio protocol, identical to Cursor and Claude Desktop.
Model | Context | RAM | Tool Calling |
| 32K | 8GB | ✅ |
| 32K | 7GB | ✅ |
| 8K | 3GB | ✅ |
For 8K context models, use --mode progressive or --mode semantic.
Command | Description |
| List available tools |
| Switch tool mode |
| Read and analyze a file |
| Clear conversation |
| Quit |
Development
make dev # Install dev dependencies
make check # Lint + type check
make test # Run tests
make pre-commit # All checks before commitSee make help for all commands. For detailed setup, see docs/DEVELOPMENT.md.
Roadmap
Component | Status | Description |
TrainerClient | ✅ Available | 16 training tools |
OptimizerClient | 🔲 Planned | Katib hyperparameter tuning |
ModelRegistryClient | 🔲 Planned | Model versioning |
See ROADMAP.md for details.
For MCP clients, agent frameworks, and production Kubernetes companions (Kyverno, ingress/OIDC, observability) — and what this project supports in-repo vs at deploy time — see Ecosystem and platform integrations in the roadmap.
Contributing
git clone https://github.com/kubeflow/mcp-server.git
cd mcp-server
make dev && make pre-commitLook for good first issue labels.
Doc | Description |
Guidelines, DCO, code style | |
System design | |
Local setup, testing | |
Security policy | |
Phases, priorities, ecosystem integrations |
Community
Slack: #kubeflow-ml-experience on CNCF Slack
Meetings: Kubeflow SDK and ML Experience bi-weekly
License
Apache-2.0
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- 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/abhijeet-dhumal/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server