Skip to main content
Glama
Thdahwache

Komodo MCP Server

by Thdahwache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Komodo MCP Server

No user-submitted related servers found.

    Related Servers

    • komodo-mcp

      digital-grease
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that exposes the full API of the Komodo infrastructure management platform. It enables users to manage deployments, stacks, servers, and containers through tools for inspection, configuration, and operational control.
      MIT

    • komodo-mcp

      MyrikLD
      F
      license
      Not graded
      quality
      C
      maintenance
      Manage Komodo DevOps platform resources (servers, containers, stacks, builds) directly from AI assistants via MCP protocol. Supports OAuth 2.1 and easy Docker Compose deployment.
      16
      -

    • Promethean OS MCP

      octave-commons
      F
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server with composable tools for GitHub operations, file management, shell execution, kanban boards, Discord messaging, and package management. Features role-based security, HTTP/stdio transports, and a web-based development UI.
      -

    • Komodo MCP Server

      Secure-ISS
      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.
      -

    • Coolify MCP Server

      wrediam
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides integration with the Coolify API, enabling DevOps teams to manage Coolify deployments, applications, services, and servers through MCP tools.
      32
      211 npm
      46
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 29 tools

    Disambiguation5/5

    Each tool maps to a distinct resource+action combination (list/get/create/update/delete across servers, builds, stacks, deployments, plus run/stop and auth). Descriptions clearly delineate scope with unique arguments, leaving no realistic confusion between tools.

    Naming Consistency5/5

    All tools follow the same 'komodo_verb_noun' snake_case pattern (komodo_list_servers, komodo_create_build, komodo_run_deployment, komodo_execute_command). The convention is applied uniformly with no deviations.

    Tool Count4/5

    29 tools is on the heavier side, but the surface spans multiple resource families (servers, builds, stacks, deployments, API keys) each needing CRUD, plus execution and auth. The count is justified by breadth rather than redundancy, though it could be slightly trimmed.

    Completeness4/5

    CRUD is well covered for servers, builds, stacks, and deployments, with run/stop for builds and deployments and full auth/API-key management. Minor gaps: stacks lack run/stop actions despite being runnable resources, and stacks/servers lack terminal-style operations, but agents can work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources