Komodo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KOMODO_ADDRESS | Yes | Base URL of your Komodo instance (e.g., https://komodo.example.com) | |
| KOMODO_API_KEY | Yes | Your Komodo API key | |
| KOMODO_API_SECRET | Yes | Your Komodo API secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| komodo_loginB | Login to Komodo and obtain authentication token. Args: username: Username for authentication password: Password for authentication Returns: Authentication response containing token and user information |
| komodo_list_api_keysB | List all API keys for the current user. Returns: List of API keys with their metadata |
| komodo_create_api_keyA | Create a new API key for the current user. Args: name: Name/label for the API key Returns: Created API key information including the key and secret |
| komodo_delete_api_keyC | Delete an API key. Args: key_id: ID of the API key to delete Returns: Deletion confirmation |
| komodo_get_deploymentB | Get detailed information about a specific deployment. Args: deployment: Deployment ID Returns: Deployment information including configuration and status |
| komodo_list_deploymentsB | List all deployments. Returns: List of all deployments with their basic information |
| komodo_get_buildB | Get detailed information about a specific build. Args: build: Build ID Returns: Build information including configuration and status |
| komodo_list_buildsB | List all builds. Returns: List of all builds with their basic information |
| komodo_get_stackC | Get detailed information about a specific stack. Args: stack: Stack ID Returns: Stack information including configuration |
| komodo_list_stacksB | List all stacks. Returns: List of all stacks with their basic information |
| komodo_get_serverA | Get detailed information about a specific server. Args: server: Server ID Returns: Server information including configuration and status |
| komodo_list_serversB | List all servers. Returns: List of all servers with their basic information |
| komodo_create_deploymentC | Create a new deployment. Args: config: Deployment configuration dictionary Returns: Created deployment information |
| komodo_update_deploymentC | Update an existing deployment. Args: id: Deployment ID config: Updated deployment configuration dictionary Returns: Updated deployment information |
| komodo_delete_deploymentC | Delete a deployment. Args: id: Deployment ID Returns: Deletion confirmation |
| komodo_create_buildC | Create a new build. Args: config: Build configuration dictionary Returns: Created build information |
| komodo_update_buildC | Update an existing build. Args: id: Build ID config: Updated build configuration dictionary Returns: Updated build information |
| komodo_delete_buildC | Delete a build. Args: id: Build ID Returns: Deletion confirmation |
| komodo_create_stackC | Create a new stack. Args: config: Stack configuration dictionary Returns: Created stack information |
| komodo_update_stackC | Update an existing stack. Args: id: Stack ID config: Updated stack configuration dictionary Returns: Updated stack information |
| komodo_delete_stackC | Delete a stack. Args: id: Stack ID Returns: Deletion confirmation |
| komodo_create_serverC | Create a new server. Args: config: Server configuration dictionary Returns: Created server information |
| komodo_update_serverC | Update an existing server. Args: id: Server ID config: Updated server configuration dictionary Returns: Updated server information |
| komodo_delete_serverC | Delete a server. Args: id: Server ID Returns: Deletion confirmation |
| komodo_run_buildB | Execute/run a build. Args: build: Build ID to execute options: Optional execution options (e.g., environment variables, timeout) Returns: Build execution result and status |
| komodo_run_deploymentB | Execute/run a deployment. Args: deployment: Deployment ID to execute options: Optional execution options (e.g., environment variables, timeout) Returns: Deployment execution result and status |
| komodo_stop_buildB | Stop a running build. Args: build: Build ID to stop Returns: Stop confirmation |
| komodo_stop_deploymentA | Stop a running deployment. Args: deployment: Deployment ID to stop Returns: Stop confirmation |
| komodo_execute_commandB | Execute a command on a server via terminal. Args: server: Server ID where the command should be executed command: Command to execute (e.g., 'ls -la', 'docker ps') options: Optional execution options (e.g., working directory, timeout, environment variables) Returns: Command execution result including stdout, stderr, and exit code |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
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.
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.
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.
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.