GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
KOMODO_URL, KOMODO_API_KEY, KOMODO_API_SECRET, KOMODO_USERNAME, KOMODO_PASSWORDValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"komodo": {
"command": "npx",
"args": [
"-y",
"komodo-mcp-server"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "your-value",
"KOMODO_USERNAME": "your-value",
"KOMODO_PASSWORD": "your-value"
}
}
}
}Run this in your terminal
claude mcp add komodo --env KOMODO_URL=your-value --env KOMODO_API_KEY=your-value --env KOMODO_API_SECRET=your-value --env KOMODO_USERNAME=your-value --env KOMODO_PASSWORD=your-value -- npx -y komodo-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"komodo": {
"command": "npx",
"args": [
"-y",
"komodo-mcp-server"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "your-value",
"KOMODO_USERNAME": "your-value",
"KOMODO_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"komodo": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"komodo-mcp-server"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "your-value",
"KOMODO_USERNAME": "your-value",
"KOMODO_PASSWORD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account MP-Tool, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: KOMODO_URL, KOMODO_API_KEY, KOMODO_API_SECRET, KOMODO_USERNAME, KOMODO_PASSWORD
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.5.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Model Context Protocol Server for [Komodo](https://github.com/moghtech/komodo)
Manage your Docker or Podman deployments through Komodo with AI assistants and automation tools.
Komodo MCP Server enables seamless interaction between AI assistants (like Claude, GitHub Copilot) and Komodo (Container Management Platform) for efficient container management, server orchestration, and deployment operations. The MCP-Server gives you the ability to control your Komodo-managed infrastructure by using natural language or automated workflows.
Features • Quick Start • Authentication • Documentation
amd64, arm64, arm/v7, and arm/v6 (Raspberry Pi). Non-root, multi-stage builds with tini init.*_FILE variants.[komodo] connection is configured once at startup (or via env vars) and used only for stdio or auth-disabled deployments.MCP_CONFIRM_DESTRUCTIVE / MCP_CONFIRM_FALLBACK./health and /ready endpoints. komodo_health_check reports server version, connectivity, and auth status.*Built on mcp-server-framework — a production-ready TypeScript MCP server framework with structured logging, OpenTelemetry, and session management.*
| Category | Tools |
|---|---|
| Configuration | komodo_health_check |
| Containers | komodo_container_list, komodo_container_inspect, komodo_container_logs, komodo_container_search_logs, komodo_container_action *(start/stop/restart/pause/unpause)* |
| Servers | komodo_server_list, komodo_server_info, komodo_server_stats, komodo_server_apply *(create/update)*, komodo_server_delete, komodo_server_action *(start_all/restart_all/pause_all/unpause_all/stop_all\_containers, prune\_\*, delete\_network/image/volume)* |
| Stacks | komodo_stack_list, komodo_stack_info, komodo_stack_apply *(create/update)*, komodo_stack_delete, komodo_stack_action *(deploy/pull/start/restart/pause/unpause/stop/destroy)* |
| Deployments | komodo_deployment_list, komodo_deployment_info, komodo_deployment_apply *(create/update)*, komodo_deployment_delete, komodo_deployment_action *(deploy/pull/start/restart/pause/unpause/stop/destroy)* |
| Builds | komodo_build_list, komodo_build_info, komodo_build_action *(run/cancel)*, komodo_build_logs, komodo_build_apply *(create/update)*, komodo_build_delete |
| Repos | komodo_repo_list, komodo_repo_info, komodo_repo_action *(clone/pull/build/cancel_build)*, komodo_repo_apply *(create/update)*, komodo_repo_delete |
| Procedures | komodo_procedure_list, komodo_procedure_info, komodo_procedure_action *(run)*, komodo_procedure_apply *(create/update)*, komodo_procedure_delete |
| Actions | komodo_action_list, komodo_action_info, komodo_action_action *(run/cancel)*, komodo_action_apply *(create/update)*, komodo_action_delete |
| Alerters | komodo_alerter_list, komodo_alerter_info, komodo_alerter_apply *(create/update)*, komodo_alerter_delete |
| Swarms | komodo_swarm_list, komodo_swarm_info, komodo_swarm_apply *(create/update)*, komodo_swarm_delete, komodo_swarm_nodes_list, komodo_swarm_services_list, komodo_swarm_action *(update_node/remove_nodes/remove_services/remove_stacks)* |
| Resource Syncs | komodo_resource_sync_list, komodo_resource_sync_info, komodo_resource_sync_action *(run/refresh)*, komodo_resource_sync_apply *(create/update)*, komodo_resource_sync_delete |
| Variables | komodo_variable_list, komodo_variable_info, komodo_variable_apply *(create/update — value/description/is_secret)*, komodo_variable_delete |
| Updates | komodo_update_list *(filterable, paginated)*, komodo_update_info |
| Terminal | komodo_exec *(target: server / container / deployment / stack_service)* |
| API Keys | komodo_user_list_api_keys, komodo_user_create_api_key, komodo_user_delete_api_key |
| Docker | komodo_docker_image_list, komodo_docker_image_inspect, komodo_docker_image_history, komodo_docker_network_list, komodo_docker_network_inspect, komodo_docker_volume_list, komodo_docker_volume_inspect |
| Builders | komodo_builder_list, komodo_builder_info, komodo_builder_apply *(create/update)*, komodo_builder_copy, komodo_builder_rename, komodo_builder_delete |
| Tags | komodo_tag_list, komodo_tag_info, komodo_tag_apply *(create/update)*, komodo_tag_delete |
| TOML Export | komodo_toml_export_all, komodo_toml_export_resources |
Tip: Every tool carries
_meta.category(one ofconfig,container,server,stack,deployment,build,repo,procedure,action,alerter,swarm,resource_sync,variable,update,terminal,user,docker,builder,tag,toml) and arequiredScopesarray (komodo:read/komodo:operate/komodo:admin), so MCP clients and gateways can filter or gate tools by category and three-tier RBAC.
Limit the tool surface (server-side). To keep a client's tool list - and its token cost - small, prune what the server registers with three optional env vars:
MCP_TOOLS_ALLOWED_CATEGORIES(category allowlist; unset -> all),MCP_TOOLS_EXCLUDED_CATEGORIES(drop whole categories), andMCP_TOOLS_EXCLUDED_TOOLS(drop tools by name, e.g.komodo_exec). Use the exact category strings above. Pruned tools are absent fromtools/listand not callable. This is purely subtractive - it never exposes more and never bypasses authentication or the read-only-when-open behavior.
List/info/logs tools support cursor pagination via
{ cursor, page_size }(1–100, default 25) and emit_meta.page.next_cursorwhen more items are available.inspect,info,logs, andsearch_logsresponses also include a session-scopedephemeral://...resource link so large payloads can be fetched out-of-band viaresources/read; passinline_full: trueto force inlining.
Deploy as a persistent HTTP server — connect from any MCP client.
mkdir komodo-mcp && cd komodo-mcp
curl -O https://raw.githubusercontent.com/MP-Tool/komodo-mcp-server/main/docker/compose.yaml curl -O https://raw.githubusercontent.com/MP-Tool/komodo-mcp-server/main/docker/docker.env cp docker.env .env # Edit with your credentials docker compose up -d
-> [Full Docker Guide](docker/README.md)
Add to your claude_desktop_config.json (Settings -> Developer -> Edit Config):
"komodo-mcp-server": {
"command": "docker", "args": [ "run", "-i", "--rm", "-e", "KOMODO_URL=https://komodo.example.com:9120", "-e", "KOMODO_API_KEY=api-key", "-e", "KOMODO_API_SECRET=api-secret", "ghcr.io/mp-tool/komodo-mcp-server:latest" ] }
-> [Full Claude Guide](examples/claude/README.md)
Add to .vscode/mcp.json in your workspace:
{
"servers": { "Komodo MCP Server": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "-e", "KOMODO_URL=https://komodo.example.com:9120", "-e", "KOMODO_API_KEY=api-key", "-e", "KOMODO_API_SECRET=api-secret", "ghcr.io/mp-tool/komodo-mcp-server:latest" ] } } }
-> [Full VS Code Guide](examples/vscode/README.md) · [Node.js / npx (no Docker)](examples/node/README.md) · [All Integrations](examples/README.md)
Once connected, ask Claude, Copilot, or any MCP-compatible assistant in plain language — it picks the tools. The tool each prompt drives is shown on the right:
| Prompt | Tool(s) called |
|---|---|
| "List all my Komodo servers" | komodo_server_list |
| "Show containers on production-server" | `kom
Only the beginning is shown; read the rest in the repo