Skip to main content
Glama

Komodo MCP Server

Un servidor MCP (Model Context Protocol) completo para la API de Komodo. Proporciona acceso a todas las funcionalidades de Komodo a través de una arquitectura modular y bien estructurada.

🚀 Despliegue Rápido (Docker Compose)

La forma más sencilla de ejecutar este servidor es utilizando Docker Compose con la imagen pre-construida.

  1. Crea un archivo docker-compose.yml:

version: '3.8'

services:
  komodo-mcp:
    image: ghcr.io/nonetss/komodo-mcp:latest
    container_name: komodo-mcp-server
    ports:
      - "3333:3333"
      - "8090:8090"
    environment:
      - KOMODO_URL=${KOMODO_URL}
      - KOMODO_KEY=${KOMODO_KEY}
      - KOMODO_SECRET=${KOMODO_SECRET}
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3333/sse"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 40s
  1. Crea un archivo .env:

KOMODO_URL=https://tu-instancia.komo.do
KOMODO_KEY=tu_api_key
KOMODO_SECRET=tu_secret
  1. Inicia el servidor:

docker compose up -d
  1. Verifica la conexión:

curl http://localhost:3333/sse

Related MCP server: PlugLayer MCP Server

🛠️ Herramientas Disponibles

El servidor MCP proporciona 40+ herramientas organizadas en los siguientes módulos:

🖥️ Servidores

  • list_servers, get_server_info, create_server, update_server, delete_server, get_server_stats

📚 Stacks

  • list_stacks, get_stack_info, deploy_stack, create_stack, update_stack, delete_stack, start_stack, stop_stack, restart_stack

🚀 Deployments

  • list_deployments, get_deployment_info, deploy_deployment, create_deployment, update_deployment, delete_deployment, start_deployment, stop_deployment, restart_deployment, get_deployment_logs

🔨 Builds

  • list_builds, get_build_info, run_build, create_build, update_build, delete_build, cancel_build

📁 Repositorios

  • list_repos, get_repo_info, create_repo, update_repo, delete_repo, pull_repo, clone_repo

⚙️ Procedimientos

  • list_procedures, get_procedure_info, run_procedure, create_procedure, update_procedure, delete_procedure

🔧 Sistema

  • list_updates, get_system_info, get_version, list_alerters, get_alerter_info, create_alerter, update_alerter, delete_alerter

🏗️ Desarrollo Local

Si deseas contribuir o modificar el código:

  1. Instala dependencias: pnpm install

  2. Desarrollo: pnpm dev

  3. Construir: pnpm build

🔗 Enlaces

Available Tools

54 tools
cancel_buildB

Cancela un build en ejecución

Inputs: build_name (required).

clone_repoD

Clona un repositorio

Inputs: repo_name (required).

create_alerterC

Crea un nuevo alerter en Komodo

Inputs: name (required), webhook_url (required), enabled, tags.

create_buildC

Crea un nuevo build en Komodo

Inputs: name (required), builder_id (required), repo (required), branch, +3 more.

create_deploymentB

Crea un nuevo deployment en Komodo

Inputs: name (required), server_id (required), image (required), environment, +4 more.

create_procedureC

Crea un nuevo procedimiento en Komodo

Inputs: name (required), stages (required), tags.

create_repoC

Crea un nuevo repositorio en Komodo

Inputs: name (required), git_provider (required), git_account (required), repo (required), +2 more.

create_serverB

Crea un nuevo servidor en Komodo

Inputs: name (required), address (required), region, enabled, +2 more.

create_stackC

Crea un nuevo stack en Komodo

Inputs: name (required), server_id (required), file_paths, git_provider, +5 more.

delete_alerterC

Elimina un alerter de Komodo

Inputs: alerter_id (required).

delete_buildB

Elimina un build de Komodo

Inputs: build_id (required).

delete_deploymentC

Elimina un deployment de Komodo

Inputs: deployment_id (required).

delete_procedureB

Elimina un procedimiento de Komodo

Inputs: procedure_id (required).

delete_repoC

Elimina un repositorio de Komodo

Inputs: repo_id (required).

delete_serverC

Elimina un servidor de Komodo

Inputs: server_id (required).

delete_stackB

Elimina un stack de Komodo

Inputs: stack_id (required).

deploy_deploymentC

Despliega un deployment específico

Inputs: deployment_name (required), stop_time.

deploy_stackC

Despliega un stack específico

Inputs: stack_name (required), stop_time.

get_alerter_infoA

Obtiene información detallada de un alerter específico

Inputs: alerter_name (required).

get_build_infoC

Obtiene información detallada de un build específico

Inputs: build_name (required).

get_deployment_infoC

Obtiene información detallada de un deployment específico

Inputs: deployment_name (required).

get_deployment_logsC

Obtiene los logs de un deployment

Inputs: deployment_name (required), tail.

get_procedure_infoC

Obtiene información detallada de un procedimiento específico

Inputs: procedure_name (required).

get_repo_infoC

Obtiene información detallada de un repositorio específico

Inputs: repo_name (required).

get_server_infoC

Obtiene información detallada de un servidor específico

Inputs: server_id (required).

get_server_statsC

Obtiene estadísticas de un servidor específico

Inputs: server_id (required).

get_stack_infoB

Obtiene información detallada de un stack específico

Inputs: stack_name (required).

get_system_infoC

Obtiene información del sistema Komodo

Inputs: no named parameters.

get_versionB

Obtiene la versión del sistema Komodo

Inputs: no named parameters.

list_alertersA

Lista todos los alerters disponibles

Inputs: no named parameters.

list_buildsA

Lista todos los builds disponibles en Komodo

Inputs: no named parameters.

list_deploymentsB

Lista todos los deployments disponibles en Komodo

Inputs: no named parameters.

list_proceduresB

Lista todos los procedimientos disponibles en Komodo

Inputs: no named parameters.

list_reposA

Lista todos los repositorios disponibles en Komodo

Inputs: no named parameters.

list_secretsB

Lista todos los secretos disponibles

Inputs: no named parameters.

list_serversA

Lista todos los servidores disponibles en Komodo

Inputs: no named parameters.

list_stacksB

Lista todos los stacks disponibles en Komodo

Inputs: no named parameters.

list_updatesC

Lista las actualizaciones recientes

Inputs: limit.

pull_repoB

Actualiza un repositorio desde el origen remoto

Inputs: repo_name (required).

restart_deploymentC

Reinicia un deployment

Inputs: deployment_name (required).

restart_stackC

Reinicia un stack

Inputs: stack_name (required).

run_buildC

Ejecuta un build específico

Inputs: build_name (required).

run_procedureC

Ejecuta un procedimiento específico

Inputs: procedure_name (required).

start_deploymentA

Inicia un deployment detenido

Inputs: deployment_name (required).

start_stackC

Inicia un stack detenido

Inputs: stack_name (required).

stop_deploymentC

Detiene un deployment en ejecución

Inputs: deployment_name (required).

stop_stackB

Detiene un stack en ejecución

Inputs: stack_name (required).

update_alerterC

Actualiza la configuración de un alerter existente

Inputs: alerter_id (required), config, tags.

update_buildC

Actualiza la configuración de un build existente

Inputs: build_id (required), config, tags.

update_deploymentC

Actualiza la configuración de un deployment existente

Inputs: deployment_id (required), config, tags.

update_procedureB

Actualiza la configuración de un procedimiento existente

Inputs: procedure_id (required), config, tags.

update_repoB

Actualiza la configuración de un repositorio existente

Inputs: repo_id (required), config, tags.

update_serverB

Actualiza la configuración de un servidor existente

Inputs: server_id (required), config, description, tags.

update_stackB

Actualiza la configuración de un stack existente

Inputs: stack_id (required), config, tags.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 54 tools

    Disambiguation5/5

    Each tool targets a distinct resource type (alerter, build, deployment, etc.) with clear actions (create, delete, get, list, update, plus specific operations like deploy, run, start, stop). No two tools have overlapping purposes, making it easy for an agent to select the correct one.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_object pattern (e.g., create_build, get_deployment_info, list_servers). No mixing of styles or irregular names, ensuring predictability.

    Tool Count2/5

    With 54 tools, this server exceeds the 'too many' threshold of 25+. While the tools are systematic and the domain is broad, the sheer number may overwhelm agents and suggests potential for consolidation.

    Completeness4/5

    The tool set covers CRUD operations for most resources (alerters, builds, deployments, procedures, repos, servers, stacks) and additional lifecycle actions. However, secrets have only a list tool, lacking create/update/delete, which is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables natural language management of servers, deployments, and build pipelines through the Komodo infrastructure platform. It provides over 60 tools for automated workflows, real-time monitoring, and secure HMAC-authenticated infrastructure control.
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT