Komodo MCP Server

NPM · KOMODO-MCP-SERVER · 2 COMPONENTS · SCANNED AUG 3

MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI

Available components

npm · komodo-mcp-server 78 oci · ghcr.io/mp-tool/komodo-mcp-server:1.4.1 9

+53 this week 78 78 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security79

No malware found by supply-chain analysis.Pass
CVE check failed: a known high-severity CVE affects @opentelemetry/propagator-jaeger 2.8.0, reached via mcp-server-framework > @opentelemetry/sdk-node > @opentelemetry/propagator-jaeger. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (176 of 184), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Cryptographically verified build provenance (signed, bound to MP-Tool/komodo-mcp-server). View diagnostics → Pass
Clear OSI-approved license (GPL-3.0).Pass
Actively maintained (last published 41 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 6981 tokens (~99/item across 70 items; 70 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · komodo-mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add mp-tool-komodo-mcp-server -- npx -y komodo-mcp-server

# add to Codex CLI

codex mcp add mp-tool-komodo-mcp-server -- npx -y komodo-mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mp-tool-komodo-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "komodo-mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add mp-tool-komodo-mcp-server --command npx --arg -y --arg komodo-mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  mp-tool-komodo-mcp-server:
    command: "npx"
    args: ["-y", "komodo-mcp-server"]

// mcp.json

{
  "mcpServers": {
    "mp-tool-komodo-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "komodo-mcp-server"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
2 Aug 26 +38
- Known CVEs: unverified → fail ▼ security
- Provenance: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: MP-Tool/komodo-mcp-server security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: GPL-3.0 functional
1 Aug 26 +31
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: unverified → fail ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
31 Jul 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −82
- Provenance: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Known CVEs: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- CVE-2026-59892 no longer affects this package ▲ security
- The attested source repository moved: MP-Tool/komodo-mcp-server security
- Maintenance: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Licence: GPL-3.0 functional
29 Jul 26 +12
- Schema quality: unverified → excellent ▲ functional
28 Jul 26 +53
- CVE-2026-59892 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- The attested source repository moved: MP-Tool/komodo-mcp-server security
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Maintenance: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- Licence: GPL-3.0 functional
26 Jul 26 25

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:: MP-Tool/komodo-mcp-server
Certificate issuer:: https://token.actions.githubusercontent.com
Certificate SAN:: https://github.com/MP-Tool/komodo-mcp-server/.github/workflows/publish-npm.yml@refs/heads/main
Rekor log index:: 1913549996
Predicate type:: https://slsa.dev/provenance/v1
Subject digest:: sha512:872ac58c7ad32da5b481c68069b5775b35ef489a055faa58ddc28774ff3f84d387492cc6c5292334ededeae2f7fd938e94aa3dde7996d26c26dd2c844
Discovery method:: attestation_endpoint

Vulnerabilities 1 finding

ID	CVE	Severity	Vector	Fix available
GHSA-45rx-2jwx-cxfr	CVE-2026-59892	high	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H	yes

Dependencies 176 packages

176 packages in the resolved dependency tree · 172 deprecated · 41 stale · 1 without a linked repository.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 70 exposed · ~6,981 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

komodo_action_action ~98

Run a Komodo Action end-to-end (long-running — polls until the underlying Update reaches Complete and returns the run logs). action='run' is currently the only verb.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Action to perform.
action_id	string	yes	Action id or name to run
args	object	—	Optional custom arguments merged on top of the Action's default arguments (exposed as `ARGS` in the script)

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_action_apply ~147

Create or update a Komodo Action (PATCH-style). An Action is a scheduled Deno/TypeScript script that runs against the Komodo API. action="create": new Action. Required: name. action="update": existing Action (`action_id` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new Action, 'update' to PATCH an existing one
action_id	string	—	Required when action='update' — existing Action id or name
config	object	—	Action configuration (PATCH-style)
name	string	—	Required when action='create' — unique name for the new Action

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_action_delete ~39

Unregister an Action from Komodo. Cancels any future scheduled runs.

Input Output Examples

Name	Type	Req	Description
action_id	string	yes	Action id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_action_info ~81

Get the full Komodo Action resource (script body, schedule, webhook config). The TypeScript script body is offloaded via a session-scoped resource link when available.

Input Output Examples

Name	Type	Req	Description
action_id	string	yes	Action id or name
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.

Name	Type	Req	Description
info	—	—	Full Action resource (only when not offloaded as a resource link)
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_action_list ~84

List all Actions registered in Komodo. An Action is a scheduled Deno/TypeScript script that runs against the Komodo API.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Actions registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_alerter_apply ~179

Create or update a Komodo Alerter (PATCH-style). Alerters route monitoring alerts to external sinks (Slack, Discord, custom HTTP, ...). action="create": new alerter. Required: name. Provide `config.endpoint` with discriminated `type` and provider params. action="update": existing alerter (`alerter` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new alerter, 'update' to PATCH an existing one
alerter	string	—	Required when action='update' — existing alerter id or name
config	object	—	Alerter configuration (PATCH-style)
name	string	—	Required when action='create' — unique name for the new alerter

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_alerter_delete ~50

Unregister an Alerter from Komodo. Future alerts that would have been routed here are dropped.

Input Output Examples

Name	Type	Req	Description
alerter	string	yes	Alerter id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_alerter_info ~89

Get the full Komodo Alerter resource (endpoint configuration, alert filters, maintenance windows). Sensitive fields like webhook URLs are offloaded via a session-scoped resource link when available.

Input Output Examples

Name	Type	Req	Description
alerter	string	yes	Alerter id or name
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.

Name	Type	Req	Description
info	—	—	Full Alerter resource (only when not offloaded as a resource link)
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_alerter_list ~92

List all alerters registered in Komodo. Alerters are sinks (Slack, Discord, Custom HTTP, ...) that receive alerts when monitored resources change state.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Alerters registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_build_action ~106

Run a lifecycle action on a Komodo Build. action=run: trigger build (long-running; polled to completion). action=cancel: abort in-progress build (fire-and-forget). Returns the resulting Update.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Build lifecycle action: `run` triggers a new build (long-running, polled until Complete), `cancel` aborts an in-progress build (fire-and-forget).
build	string	yes	Build id or name

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_build_apply ~155

Create or update a Komodo Build (PATCH-style). Does not trigger a build — call `komodo_build_action` run afterwards. action="create": new build. Required: name. Provide repo/branch/builder in config. action="update": existing build (`build` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new build, 'update' to PATCH an existing one
build	string	—	Required when action='update' — existing build id or name
config	object	—	Build configuration (all fields optional, PATCH-style)
name	string	—	Required when action='create' — unique name for the new build

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_build_delete ~41

Unregister a Build from Komodo. Does not delete previously pushed images from the registry.

Input Output Examples

Name	Type	Req	Description
build	string	yes	Build id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_build_info ~83

Get the full Komodo Build resource for a single build, including its configuration (builder, repo/branch, image, dockerfile, build args, labels) and last-built metadata.

Input Output Examples

Name	Type	Req	Description
build	string	yes	Build id or name
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.

Name	Type	Req	Description
info	—	—	Full build resource payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_build_list ~92

List all builds registered in Komodo. Shows build id, name, current state (Building/Ok/Failed/Unknown), version, attached builder, source repo and branch.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Builds registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_build_logs ~80

Fetch per-stage logs from a previous build run. Pass the `update_id` returned by `komodo_build_action`.

Input Output Examples

Name	Type	Req	Description
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
update_id	string	yes	Komodo Update id returned by a previous komodo_build_run call

Name	Type	Req	Description
logs	array	—	Per-stage log entries from the build run
resourceLink	object	—	Reference to a server-exposed resource
status	string	yes	Update status (Complete, InProgress, Queued)
success	boolean	yes	Overall success of the build run
summary	object	yes	—
update_id	string	yes	Komodo Update ID providing these logs

No examples provided.

komodo_configure ~152

Configure connection to Komodo Core server. Required before using any other Komodo tools. Supports three auth methods: username+password (local login), apiKey+apiSecret, or jwtToken.

Input Output Examples

Name	Type	Req	Description
apiKey	string	—	Komodo API key (for API-key auth)
apiSecret	string	—	Komodo API secret (for API-key auth)
jwtToken	string	—	Komodo JWT token (for JWT auth)
password	string	—	Komodo password (for password auth)
url	string	yes	Komodo Core server URL (e.g., http://host.docker.internal:9120)
username	string	—	Komodo username (for password auth)

Name	Type	Req	Description
auth_method	string	yes	Resolved auth method (password, api-key, jwt)
configured	boolean	yes	Whether the client connection has been established
error	string	—	Error message when the health probe failed
healthy	boolean	yes	Whether the post-connect health probe succeeded
komodo_version	string	—	Komodo Core version, when reported by the health probe
login_methods	string	—	Comma-separated login methods advertised by the server
server	string	yes	Komodo Core URL the client is bound to

No examples provided.

komodo_container_action ~129

Run a lifecycle action on a Docker container: start, stop, restart, pause, or unpause. The container must exist on the target server. Note: pause/unpause use cgroups freezer; restart is stop+start.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Lifecycle action: start (run a stopped/paused container), stop (stop a running container), restart (stop+start), pause (freeze processes), unpause (resume).
container	string	yes	Container name or ID to perform the action on
server	string	yes	Server ID or name where the container is running

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_container_inspect ~92

Get detailed low-level information about a container. Returns Docker inspect data including configuration, state, network settings, mounts, and process info.

Input Output Examples

Name	Type	Req	Description
container	string	yes	Container name or ID to inspect
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
server	string	yes	Server ID or name where the container is running

Name	Type	Req	Description
inspect	—	—	Raw Docker inspect payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_container_list ~97

List all containers on a server, including running, stopped, and paused containers. Shows container name, state, and image.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.
server	string	yes	Server ID or name to list containers from

Name	Type	Req	Description
items	array	yes	Containers on the target server
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_container_logs ~125

Get stdout and stderr logs from a container. Useful for debugging, monitoring application output, and troubleshooting issues.

Input Output Examples

Name	Type	Req	Description
container	string	yes	Container name or ID to get logs from
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
server	string	yes	Server ID or name where the container is running
tail	integer	—	Number of lines to show from the end of logs. Default: 100
timestamps	boolean	—	Show timestamps in log output. Default: false

Name	Type	Req	Description
resourceLink	object	—	Reference to a server-exposed resource
stderr	string	—	Captured stderr content (may be truncated)
stdout	string	—	Captured stdout content (may be truncated)
summary	object	yes	—
truncated	boolean	—	True when the log output was truncated by the tail limit

No examples provided.

komodo_container_search_logs ~170

Search container logs for specific patterns or keywords. Retrieves logs and filters them client-side. Returns matching lines with a count of matches. Large match sets are offloaded as a session-scoped resource link unless `inline_full` is set.

Input Output Examples

Name	Type	Req	Description
caseSensitive	boolean	—	Perform case-sensitive search. Default: false
container	string	yes	Container name or ID to search logs from
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
query	string	yes	Search query or pattern to filter logs (plain text, not regex)
server	string	yes	Server ID or name where the container is running
tail	integer	—	Number of lines to retrieve before filtering. Default: 1000

Name	Type	Req	Description
matches	array	yes	Matched log lines
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—
truncated	boolean	—	True when the search window was truncated by the tail limit

No examples provided.

komodo_deployment_action ~123

Lifecycle action on a deployment: deploy (recreate container), pull (image only), start, restart, pause, unpause, stop, destroy (remove container). destroy is destructive; config preserved.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Lifecycle action: deploy (create or re-deploy the container), pull (pull image without recreating), start (start a stopped container), restart (stop+start), pause/unpause (freeze/resume processes), s…
deployment	string	yes	Deployment ID or name

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_deployment_apply ~217

Create or update a Komodo deployment (Docker container, PATCH-style). action="create": new deployment. Required: name. Recommended: server_id, image. action="update": existing deployment (`deployment` required). Only fields in `config` change. Image accepts a string ("nginx:1.25") or { type: "Image"|"Build", params: {…} }.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new deployment, 'update' to PATCH an existing one
config	object	—	Deployment configuration fields to update (partial update)
deployment	string	—	Required when action='update' — existing deployment id or name
image	—	—	Convenience field for action='create' — Docker image to deploy (mirrors `config.image`)
name	string	—	Required when action='create' — unique name for the new deployment
server_id	string	—	Convenience field for action='create' — target server (mirrors `config.server_id`)

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_deployment_delete ~40

Delete a Komodo deployment. Removes the deployment configuration and stops/removes the associated container.

Input Output Examples

Name	Type	Req	Description
deployment	string	yes	Deployment ID or name

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_deployment_info ~72

Get detailed information about a Komodo-managed deployment, including its configuration, current state, and assigned server.

Input Output Examples

Name	Type	Req	Description
deployment	string	yes	Deployment ID or name to get info for
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.

Name	Type	Req	Description
info	—	—	Full deployment resource payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_deployment_list ~86

List all Komodo-managed deployments. Deployments are single-container applications managed by Komodo. Shows deployment name, ID, and current state.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Deployments visible to the caller
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_exec ~261

Execute a shell command on a Komodo target. `target` selects the context: server (server[, shell, terminal]) | container (server, container[, shell]) | deployment (deployment[, shell]) | stack_service (stack, service[, shell]). Output ≤50 KB; timeout 5 min.

Input Output Examples

Name	Type	Req	Description
command	string	yes	The shell command to execute
container	string	—	Required for 'container': container name or id
deployment	string	—	Required for 'deployment': deployment id or name
server	string	—	Required for 'server' / 'container': Komodo server id or name
service	string	—	The service name within the stack to execute the command in
shell	string	—	The shell to use for execution (e.g. 'sh', 'bash', '/bin/zsh'). For 'server' target: used as the terminal init command. Default: sh
stack	string	—	Required for 'stack_service': stack id or name
target	string	yes	Execution context: server \| container \| deployment \| stack_service
terminal	string	—	Terminal session name on the server. If it doesn't exist, it will be created. Default: mcp

Name	Type	Req	Description
command	string	yes	The shell command that was executed
container	string	—	Container, when target = container
deployment	string	—	Deployment, when target = deployment
exit_code	string\|null	yes	Exit code reported by Komodo, or null when unknown
output	string	yes	Combined stdout/stderr stream as captured (may be truncated)
server	string	—	Server context, when the target requires it
service	string	—	Service name within the stack, when target = stack_service
stack	string	—	Stack, when target = stack_service
target	string	yes	Execution context that ran
truncated	boolean	yes	True when the output buffer was truncated by size or timeout

No examples provided.

komodo_health_check ~38

Check the Komodo connection status. Returns health, authentication status, and API version. Works without an active connection (reports unconfigured state).

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
configured	boolean	yes	Whether a Komodo client connection has been configured
error	string	—	Error message when the health probe failed
healthy	boolean	yes	Whether the Komodo server responded successfully to a health probe
komodo_version	string	—	Komodo Core version reported by the health probe
mcp_server_version	string	yes	Version of this MCP server
server	string	—	Komodo Core URL the client is bound to, when configured

No examples provided.

komodo_procedure_action ~68

Procedure action. action='run': run a Komodo Procedure end-to-end (long-running — polls until the underlying Update reaches Complete and returns the per-stage logs).

Input Output Examples

Name	Type	Req	Description
action	string	yes	Action to perform on the procedure.
procedure	string	yes	Procedure id or name

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_procedure_apply ~144

Create or update a Komodo Procedure (PATCH-style). A procedure is a multi-stage workflow run manually or on schedule. action="create": new procedure. Required: name. action="update": existing procedure (`procedure` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new procedure, 'update' to PATCH an existing one
config	object	—	Procedure configuration (all fields optional, PATCH-style)
name	string	—	Required when action='create' — unique name for the new procedure
procedure	string	—	Required when action='update' — existing procedure id or name

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_procedure_delete ~39

Unregister a Procedure from Komodo. Cancels any future scheduled runs.

Input Output Examples

Name	Type	Req	Description
procedure	string	yes	Procedure id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_procedure_info ~61

Get the full Komodo Procedure resource (configuration, stages, schedule).

Input Output Examples

Name	Type	Req	Description
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
procedure	string	yes	Procedure id or name

Name	Type	Req	Description
info	—	—	Full Procedure resource (only when not offloaded as a resource link)
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_procedure_list ~83

List all procedures registered in Komodo. A procedure is a multi-stage workflow that can be triggered manually or on a schedule.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Procedures registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_repo_action ~90

Lifecycle action on a Komodo Repo. clone/pull/build are long-running and polled to completion. cancel_build is fire-and-forget.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Lifecycle action: clone (initial git clone on attached server), pull (git pull), build (run repo build via builder), cancel_build (cancel an in-progress build).
repo	string	yes	Repo id or name

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_repo_apply ~149

Create or update a Komodo Repo (PATCH-style). Not cloned automatically — call `komodo_repo_action` clone afterwards. action="create": new repo. Required: name. action="update": existing repo (`repo` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new repo, 'update' to PATCH an existing one
config	object	—	Repo configuration fields to update (partial update — only specified fields are changed)
name	string	—	Required when action='create' — unique name for the new repo
repo	string	—	Required when action='update' — existing repo id or name

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_repo_delete ~42

Unregister a Repo from Komodo. Does not affect the cloned working copy on the server.

Input Output Examples

Name	Type	Req	Description
repo	string	yes	Repo id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_repo_info ~61

Get the full Komodo Repo resource (configuration + last clone/build metadata).

Input Output Examples

Name	Type	Req	Description
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
repo	string	yes	Repo id or name

Name	Type	Req	Description
info	—	—	Full repo resource payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_repo_list ~92

List all repos registered in Komodo. Shows id, name, state, attached server/builder, configured repo+branch, and the cloned/built/latest short commit hashes.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Repos registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_resource_sync_action ~104

Lifecycle action on a Komodo ResourceSync. 'run' executes the sync (applies pending changes — long-running, polled). 'refresh' updates the pending-changes preview without applying anything.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Lifecycle action: 'run' executes the sync (applies pending changes — long-running, polled). 'refresh' updates the pending-changes preview without applying anything.
resource_sync	string	yes	ResourceSync id or name

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_resource_sync_apply ~192

Create or update a Komodo ResourceSync (PATCH-style on update). Not executed automatically — call `komodo_resource_sync_action` with action='run' afterwards. action="create": new sync. Required: name. Provide `config` with repo+branch+resource_path or inline file_contents. action="update": existing sync (`resource_sync` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new resource sync, 'update' to PATCH an existing one
config	object	—	ResourceSync configuration (repo, branch, resource_path[], file_contents, managed, etc.). Only specify fields you want to set or update.
name	string	—	Required when action='create' — unique name for the new resource sync
resource_sync	string	—	Required when action='update' — existing resource sync id or name

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_resource_sync_delete ~45

Unregister a ResourceSync from Komodo. Resources created via previous syncs are not removed.

Input Output Examples

Name	Type	Req	Description
resource_sync	string	yes	ResourceSync id or name to delete

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_resource_sync_info ~62

Get the full Komodo ResourceSync resource including pending diffs.

Input Output Examples

Name	Type	Req	Description
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
resource_sync	string	yes	ResourceSync id or name

Name	Type	Req	Description
info	—	—	Full resource sync payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_resource_sync_list ~84

List all resource syncs registered in Komodo. Shows configured repo+branch, managed mode, and last successful sync timestamp/hash.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	ResourceSyncs registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_server_action ~142

Host-level operations on a Komodo server: batch container lifecycle (start/restart/pause/unpause/stop all), Docker resource pruning (containers, images, volumes, networks, system, builders, buildx), or deletion of named networks/images/volumes. Destructive — frees disk space or stops workloads.

Input Output Examples

Name	Type	Req	Description
action	string	yes	Action to perform. Batch container ops act on every container on the host. Prune ops free disk space. Delete ops require `name`.
name	string	—	Required for delete_network/delete_image/delete_volume. Name of the resource to delete.
server	string	yes	Target server (id or name)

Name	Type	Req	Description
action	string	yes	Action name that was executed (start, stop, deploy, prune, ...)
resource_id	string	yes	Target resource ID or name
resource_type	string	yes	Target resource type (container, deployment, stack, server)
server	string	—	Target server, when the action runs against a host
status	string	yes	Update status reported by Komodo (Complete, InProgress, Queued, ...)
success	boolean	yes	Whether the action completed successfully
version	string	—	Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_server_apply ~144

Create or update a Komodo Server (PATCH-style; safe to call repeatedly). action="create": new server. Required: name. Periphery agent must be reachable at config.address. action="update": existing server (`server` required). Only fields in `config` change.

Input Output Examples

Name	Type	Req	Description
action	string	yes	'create' to register a new server, 'update' to PATCH an existing one
config	object	—	Server configuration fields to update (partial update)
name	string	—	Required when action='create' — unique name for the new server
server	string	—	Required when action='update' — existing server id or name

Name	Type	Req	Description
action	string	yes	Which apply action was performed
resource	object	—	Full resource returned by Komodo (when available)
resource_id	string	yes	Resource id or name affected
resource_type	string	yes	Target resource type

No examples provided.

komodo_server_delete ~29

Delete (unregister) a server

Input Output Examples

Name	Type	Req	Description
server	string	yes	Server ID or name

Name	Type	Req	Description
action	string	yes	Always 'remove' for delete tools
resource	object	—	Snapshot of the deleted resource (when available)
resource_id	string	yes	Resource id or name that was removed
resource_type	string	yes	Target resource type

No examples provided.

komodo_server_info ~54

Get detailed information about a specific server

Input Output Examples

Name	Type	Req	Description
inline_full	boolean	—	If true, return the full payload inline instead of a compact summary. Default: false.
server	string	yes	Server ID or name

Name	Type	Req	Description
info	—	—	Full server resource payload, when returned inline
resourceLink	object	—	Reference to a server-exposed resource
summary	object	yes	—

No examples provided.

komodo_server_list ~86

List all servers registered in Komodo. Shows server name, ID, status (healthy/unhealthy/disabled), Periphery version, and region.

Input Output Examples

Name	Type	Req	Description
cursor	string	—	Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_size	integer	—	Maximum number of items to return (1-100). Default: server-defined.

Name	Type	Req	Description
items	array	yes	Servers registered in Komodo
page	object	—	Pagination envelope for list responses

No examples provided.

komodo_server_stats ~57

Get server health status and state. Returns whether the Periphery agent is reachable and the server is healthy. For detailed system metrics, use komodo_server_info.

Input Output Examples

Name	Type	Req	Description
server	string	yes	Server ID or name to get stats for

Name	Type	Req	Description
resourceLink	object	—	Reference to a server-exposed resource
server	string	yes	Server ID
status	string	yes	Health status reported by Periphery

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug