MCP.Market

Komodo MCP Server

by Samik081·io.github.Samik081/mcp-komodo·v0.9.1·7 stars
No reviews yet

Manage Komodo through AI assistants

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

7 stars184 downloads/wk

Reviews

Write one

Nobody has reviewed Komodo MCP Server yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Komodo MCP Server tools (63, 18 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • komodo_cancel_buildwrite action

    Cancel a running Komodo Build. Stops the build process if it is

  • komodo_create_api_key_for_service_userwrite action

    Create an API key for a service user (admin only). The secret is returned ONCE and cannot be retrieved again

  • komodo_create_service_userwrite action

    Create a Komodo service user for automation (admin only). Follow up with komodo_create_api_key_for_service_user and permission tools

  • komodo_delete_api_key_for_service_userwrite action

    Delete a service user's API key by key ID (admin only)

  • komodo_delete_docker_resourcewrite action

    \u26a0\ufe0f DELETE a specific Docker resource (image, volume, or network)

  • komodo_delete_userwrite action

    Delete a Komodo user by ID or username (admin only). THIS CANNOT BE UNDONE

  • komodo_deploy_deploymentwrite action

    \u26a0\ufe0f DEPLOY a Komodo Deployment. This stops the current container

  • komodo_deploy_stackwrite action

    \u26a0\ufe0f DEPLOY a Komodo Stack. This redeploys all services in the stack,

  • komodo_deployment_lifecycle

    \u26a0\ufe0f LIFECYCLE: Control a Komodo Deployment's container lifecycle.

  • komodo_destroy_deploymentwrite action

    \ud83d\udd34 DESTROY a Komodo Deployment permanently. This stops the

  • komodo_destroy_stackwrite action

    \ud83d\udd34 DESTROY a Komodo Stack permanently. This stops all containers

  • komodo_get_action

    Get detailed information about a specific Komodo Action by name

  • komodo_get_alerter

    Get detailed information about a specific Komodo Alerter by name

  • komodo_get_build

    Get detailed information about a specific Komodo Build by name

  • komodo_get_builder

    Get detailed information about a specific Komodo Builder by name

  • komodo_get_container_log

    Get logs from a Docker container running on a Komodo Server.

  • komodo_get_deployment

    Get detailed information about a specific Komodo Deployment by

  • komodo_get_deployment_log

    Get logs from a Komodo Deployment's Docker container. Optionally

  • komodo_get_deployments_summary

    Get a summary of all Komodo Deployments. Returns aggregate counts

  • komodo_get_procedure

    Get detailed information about a specific Komodo Procedure by

  • komodo_get_repo

    Get detailed information about a specific Komodo Repo by name

  • komodo_get_resource_sync

    Get detailed information about a specific Komodo Resource Sync

  • komodo_get_server

    Get detailed information about a specific Komodo Server by name

  • komodo_get_server_info

    Get system information and running processes for a Komodo Server.

  • komodo_get_server_stats

    Get current resource usage statistics for a Komodo Server.

  • komodo_get_stack

    Get detailed information about a specific Komodo Stack by name

  • komodo_get_stack_log

    Get logs from a Komodo Stack's Docker Compose services. Optionally

  • komodo_get_stacks_summary

    Get a summary of all Komodo Stacks. Returns aggregate counts

  • komodo_get_updatewrite action

    Get detailed information about a specific Komodo Update (operation

  • komodo_inspect_deployment_container

    Inspect the Docker container associated with a Deployment.

  • komodo_inspect_docker_container

    Inspect a Docker container on a Komodo Server. Returns the full

  • komodo_inspect_docker_image

    Inspect a Docker image on a Komodo Server. Returns the full image

  • komodo_inspect_docker_network

    Inspect a Docker network on a Komodo Server. Returns the full

  • komodo_inspect_docker_volume

    Inspect a Docker volume on a Komodo Server. Returns the full

  • komodo_inspect_stack_container

    Inspect a Docker container for a specific service within a Stack.

  • komodo_list_actions

    List all Komodo Actions. An Action is a custom TypeScript/Deno

  • komodo_list_alerters

    List all Komodo Alerters. An Alerter is a notification endpoint

  • komodo_list_api_keys_for_service_user

    List the API keys of a service user (admin only). Secrets are never returned

  • komodo_list_builders

    List all Komodo Builders. A Builder is a build server (or AWS

  • komodo_list_builds

    List all Komodo Builds. A Build is a Docker image build

  • komodo_list_deployments

    List all Komodo Deployments. A Deployment is a single Docker

  • komodo_list_permissions

    List the permissions granted to a user or user group (admin only)

  • komodo_list_procedures

    List all Komodo Procedures. A Procedure is an orchestrated

  • komodo_list_repos

    List all Komodo Repos. A Repo is a Git repository cloned to a

  • komodo_list_resource_syncs

    List all Komodo Resource Syncs. A Resource Sync is a GitOps sync

  • komodo_list_servers

    List all Komodo Servers. A Server is a remote machine managed

  • komodo_list_stack_services

    List all services in a Komodo Stack. Returns the service name,

  • komodo_list_stacks

    List all Komodo Stacks. A Stack is a multi-container deployment

  • komodo_list_updates

    List Komodo operation history (updates). Every execute operation

  • komodo_list_users

    List Komodo users, optionally filtering service users (admin only)

  • komodo_prune_docker

    \u26a0\ufe0f PRUNE unused Docker resources on a specific Komodo Server.

  • komodo_pull_deployment

    \u26a0\ufe0f PULL the image for a Komodo Deployment (docker pull).

  • komodo_pull_stack

    \u26a0\ufe0f PULL images for a Komodo Stack (docker compose pull).

  • komodo_repo_clone_pull

    \u26a0\ufe0f CLONE or PULL a Komodo Repo on its target server. 'clone'

  • komodo_run_actionwrite action

    \u26a0\ufe0f RUN a Komodo Action. This executes a custom TypeScript/Deno

  • komodo_run_buildwrite action

    \u26a0\ufe0f RUN a Komodo Build to create a Docker image. This clones the

  • komodo_run_procedurewrite action

    \u26a0\ufe0f RUN a Komodo Procedure. This executes all stages in sequence,

  • komodo_stack_lifecycle

    \u26a0\ufe0f LIFECYCLE: Control a Komodo Stack's container lifecycle.

  • komodo_trigger_sync

    \u26a0\ufe0f TRIGGER a Komodo Resource Sync. This pulls the latest TOML

  • komodo_update_permission_on_resource_typewrite action

    Set a user or user group's base permission level on ALL resources of a type (admin only)

  • komodo_update_permission_on_targetwrite action

    Set a user or user group's permission level on ONE specific resource (admin only)

  • komodo_update_user_base_permissionswrite action

    Update a user's base flags: enabled, create servers, create builds (admin only)

  • komodo_write_resourcewrite action

    Create, update, or delete any Komodo resource. Supports all 10 resource

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan55 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 28 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Komodo MCP Server compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
63
the typical server has 7
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
7
more than 86% of 28,688 servers
Downloads a week
184
more than 74% of 12,191 servers with a package

What its tools let an agent do: 45 read · 18 change

Release history: 2 versions in the registry since 2026-09-02, latest 2026-09-29, typically one every 27 days.

Install Komodo MCP Server in Claude Code, Cursor or VS Code

Runs npx -y @samik081/mcp-komodo on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-komodo -- npx -y @samik081/mcp-komodo
Add to Cursor

What the publisher says

From the Komodo MCP Server repository's README, as published. We do not edit it. Read it on GitHub

MCP Komodo

MCP server for the Komodo DevOps platform. Manage servers, stacks, deployments, builds, and more through natural language in Cursor, Claude Code, and Claude Desktop.

Features

  • 63 tools across 14 categories covering the complete Komodo DevOps API
  • Three access tiers (read-only, read-execute, full) for granular control
  • Category filtering via KOMODO_CATEGORIES to expose only the tools you need
  • Zero HTTP dependencies -- lightweight native-fetch client, no SDK required
  • Docker images for linux/amd64 and linux/arm64 on GHCR
  • Remote MCP via HTTP transport (MCP_TRANSPORT=http) using the Streamable HTTP protocol
  • TypeScript/ESM with full type safety

API Compatibility

Built for Komodo 1.19.5.

Quick Start

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.

Docker

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.

Configuration

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

# Using Docker
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

# Using remote HTTP (connect to a running Docker container or HTTP server)
claude mcp add --transport http komodo http://localhost:3000

JSON config (works with Claude Code .mcp.json, Claude Desktop claudedesktopconfig.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"
    }
  }
}

Access Tiers

Control which tools are available using the KOMODOACCESSTIER environment variable:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Komodo MCP Server: common questions

Is Komodo MCP Server safe?
Mostly: it is graded B (83/100). Read the Komodo MCP Server safety report
How do I install Komodo MCP Server?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Komodo MCP Server need an API key?
Yes. The registry entry asks for KOMODO_API_KEY, KOMODO_API_SECRET.
Is Komodo MCP Server maintained?
The last commit was 36 days ago (2026-09-29). The latest release is v0.9.1.
How does Komodo MCP Server compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 63 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from Samik081 →