Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Manage Komodo through AI assistants
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_SECRETValues 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",
"@samik081/mcp-komodo"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "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 -- npx -y @samik081/mcp-komodoFill 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",
"@samik081/mcp-komodo"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "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",
"@samik081/mcp-komodo"
],
"env": {
"KOMODO_URL": "your-value",
"KOMODO_API_KEY": "your-value",
"KOMODO_API_SECRET": "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 8, 2026
The registry name was verified with the GitHub account Samik081, 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
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 (0.9.1) reached the registry 39 days 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: Spec Driven Development, Remote Desktop Commander, NexusWindows
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
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.
MCP server for the Komodo DevOps platform. Manage servers, stacks, deployments, builds, and more through natural language in Cursor, Claude Code, and Claude Desktop.
read-only, read-execute, full) for granular controlKOMODO_CATEGORIES to expose only the tools you needlinux/amd64 and linux/arm64 on GHCRMCP_TRANSPORT=http) using the Streamable HTTP protocolBuilt for Komodo 1.19.5.
Run the server directly with npx:
KOMODO_URL="https://komodo.example.com" \
KOMODO_API_KEY="your-api-key" \ KOMODO_API_SECRET="your-api-secret" \ npx -y @samik081/mcp-komodo
The server validates your Komodo connection on startup and fails immediately with a clear error if credentials are missing or invalid.
Run with Docker (stdio transport, same as npx):
docker run --rm -i \
-e KOMODO_URL=https://komodo.example.com \ -e KOMODO_API_KEY=your-api-key \ -e KOMODO_API_SECRET=your-api-secret \ ghcr.io/samik081/mcp-komodo
To run as a remote MCP server with HTTP transport:
docker run -d -p 3000:3000 \
-e MCP_TRANSPORT=http \ -e KOMODO_URL=https://komodo.example.com \ -e KOMODO_API_KEY=your-api-key \ -e KOMODO_API_SECRET=your-api-secret \ ghcr.io/samik081/mcp-komodo
The MCP endpoint is available at http://localhost:3000 and a health check at http://localhost:3000/health.
Claude Code CLI (recommended):
# Using npx
claude mcp add --transport stdio komodo \ --env KOMODO_URL=https://komodo.example.com \ --env KOMODO_API_KEY=your-api-key \ --env KOMODO_API_SECRET=your-api-secret \ -- npx -y @samik081/mcp-komodo
claude mcp add --transport stdio komodo \ --env KOMODO_URL=https://komodo.example.com \ --env KOMODO_API_KEY=your-api-key \ --env KOMODO_API_SECRET=your-api-secret \ -- docker run --rm -i ghcr.io/samik081/mcp-komodo
claude mcp add --transport http komodo http://localhost:3000
JSON config (works with Claude Code .mcp.json, Claude Desktop claude_desktop_config.json, Cursor .cursor/mcp.json):
{
"mcpServers": { "komodo": { "command": "npx", "args": ["-y", "@samik081/mcp-komodo"], "env": { "KOMODO_URL": "https://komodo.example.com", "KOMODO_API_KEY": "your-api-key", "KOMODO_API_SECRET": "your-api-secret" } } } }
Docker (stdio):
{
"mcpServers": { "komodo": { "command": "docker", "args": ["run", "--rm", "-i", "-e", "KOMODO_URL=https://komodo.example.com", "-e", "KOMODO_API_KEY=your-api-key", "-e", "KOMODO_API_SECRET=your-api-secret", "ghcr.io/samik081/mcp-komodo" ] } } }
Remote MCP (connect to a running Docker container or HTTP server):
{
"mcpServers": { "komodo": { "type": "streamable-http", "url": "http://localhost:3000" } } }
Control which tools are available using the KOMODO_ACCESS_TIER environment variable:
| Tier | Tools | Description |
|---|---|---|
full (default) | 63 | Read, execute, and write -- full control |
read-execute | 55 | Read and execute -- no resource creation/deletion, no user administration |
read-only | 39 | Read only -- safe for exploration, no state changes |
Tier details:
komodo_write_resource for creating, updating, and deleting Komodo resources, plus the user administration tools (service users, API keys, permissions).komodo_write_resource tool and the user administration write tools are hidden.Tools that are not available in your tier are not registered with the MCP server. They will not appear in your AI tool's tool list, keeping the context clean.
Set KOMODO_ACCESS_TIER to read-only, read-execute, or full (default: full).
| Variable | Required | Default | Description |
|---|---|---|---|
KOMODO_URL | Yes | -- | URL of your Komodo Core instance |
KOMODO_API_KEY | Yes | -- | API key for authentication |
KOMODO_API_SECRET | Yes | -- | API secret for authentication |
KOMODO_ACCESS_TIER | No | full | Access tier: read-only, read-execute, or full |
KOMODO_CATEGORIES | No | *(all)* | Comma-separated category allowlist (e.g., servers,stacks,builds) |
KOMODO_TOOL_BLACKLIST | No | *(none)* | Comma-separated list of tool names to exclude (e.g., komodo_destroy_stack) |
KOMODO_TOOL_WHITELIST | No | *(none)* | Comma-separated list of tool names to force-include, bypassing access tier and category filters |
KOMODO_ALLOW_ENV_VALUES | No | *(tier-based)* | Whether inspect tools may return plaintext env values via show_env_values: true. Defaults to allowed on read-execute/full and refused on read-only; set true or false to override |
DEBUG | No | false | Enable debug logging to stderr |
MCP_TRANSPORT | No | stdio | Transport mode: stdio (default) or http |
MCP_PORT | No | 3000 | HTTP server port (only used when MCP_TRANSPORT=http) |
MCP_HOST | No | 0.0.0.0 | HTTP server bind address (only used when MCP_TRANSPORT=http) |
MCP_SESSION_IDLE_TIMEOUT | No | 1800 | Seconds of inactivity after which an HTTP session is closed and its memory released (sessions with a connected SSE stream are never closed). 0 disables. Only used when MCP_TRANSPORT=http |
MCP_EXCLUDE_TOOL_TITLES | No | false | Set true to omit tool titles from registration (saves tokens) |
Generate API keys in the Komodo UI under Settings > API Keys.
servers, stacks, deployments, containers, builds, repos, procedures, actions, builders, alerters, resource-syncs, updates, users, write
mcp-komodo provides 63 tools organized by category. Each tool's Access column shows the minimum tier required: read-only (available in all tiers), read-execute (requires read-execute or full), or full (requires full tier only). The Hints column shows tool behavior: read-only (no state changes), destructive (modifies existing state), idempotent (same result if called twice).
All 16 execute tools wait for the operation to complete and report its real outcome by default; pass wait: false for fire-and-forget, or wait_timeout_seconds to bound the wait (default 45s).
Servers (10 tools)
| Tool | Description | Access | Hints |
|---|---|---|---|
komodo_list_servers | List all servers with status and region | read-only | read-only, idempotent |
komodo_get_server | Get server configuration, status, and action state | read-only | read-only, idempotent |
komodo_get_server_stats | Get CPU, memory, disk usage, and load averages | read-only | read-only, idempotent |
komodo_get_server_info | Get OS details, hardware info, and running processes | read-only | read-only, idempotent |
komodo_inspect_docker_container | Inspect a Docker container (docker inspect payload); env values render as sha256:<12-hex> digests unless show_env_values: true (refused on the read-only tier unless KOMODO_ALLOW_ENV_VALUES=true) -- redaction covers Env arrays only, so labels, cmd, and mounts are returned unredacted | read-only | read-only, idempotent |
komodo_inspect_docker_image | Inspect a Docker image (docker image inspect payload); baked-in env values render as sha256:<12-hex> digests unless show_env_values: true (refused on the read-only tier unless KOMODO_ALLOW_ENV_VALUES=true) -- redaction covers Env arrays only, so labels, cmd, and layers are returned unredacted | read-only | read-only, idempotent |
komodo_inspect_docker_network | Inspect a Docker network (equivalent to docker network inspect) | read-only | read-only, idempotent |
komodo_inspect_docker_volume | Inspect a Docker volume (equivalent to docker volume inspect) | read-only | read-only, idempotent |
komodo_prune_docker | Prune unused Docker resources on a server | read-execute | destructive, idempotent |
komodo_delete_docker_resource | Delete a specific Docker image, volume, or network | read-execute | destructive |
Stacks (10 tools)
| Tool | Description | Access | Hints |
|---|---|---|---|
komodo_list_stacks | List all stacks with state, server, and service count | read-only | read-only, idempotent |
komodo_get_stack | Get stack configuration, services, and action state | read-only | read-only, idempotent |
komodo_list_stack_services | List services in a stack with image, container state, and update availability | read-only | read-only, idempotent |
komodo_get_stacks_summary | Get aggregate counts of all stacks by state | read-only | read-only, idempotent |
komodo_get_stack_log | Get logs from stack services, with optional search | read-only | read-only, idempotent |
komodo_inspect_stack_container | Inspect a container for a specific service in a stack (docker inspect payload); env values render as sha256:<12-hex> digests unless show_env_values: true (refused on the read-only tier unless KOMODO_ALLOW_ENV_VALUES=true) -- redaction covers Env arrays only, so labels, cmd, and mounts are returned unredacted | read-only | read-only, idempotent |
komodo_deploy_stack | Deploy or redeploy a stack | read-execute | destructive |
komodo_pull_stack | Pull latest images without redeploying (docker compose pull) | read-execute | idempotent |
komodo_stack_lifecycle | Start, stop, restart, pause, or unpause a stack; optionally targets specific services | read-execute | destructive |
komodo_destroy_stack | Permanently destroy a stack | read-execute | destructive |
Deployments (9 tools)
| Tool | Description | Access | Hints |
|---|---|---|---|
komodo_list_deployments | List all deployments with state, image, and server | read-only | read-only, idempotent |
komodo_get_deployment | Get deployment configuration, container status, and action state | read-only | read-only, idempotent |
komodo_get_deployments_summary | Get aggregate counts of all deployments by state | read-only | read-only, idempotent |
komodo_get_deployment_log | Get container logs, with optional search | read-only | read-only, idempotent |
| komodo_inspect_deployment_container | Inspect the container for a deployment (docker inspect payload); env values render as sha256:<12-hex> digests unless show_env_values: true (refused on the read-only tier unless KOMODO_ALLOW_ENV_VALUES=true) -- redaction covers Env arrays only
Only the beginning is shown; read the rest in the repo