Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Komodo MCP Server

OCI · GHCR.IO/MP-TOOL/KOMODO-MCP-SERVER:1.5.0 · 2 COMPONENTS

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

0 this week 67 Trust /100

Last scanned (4 hours ago)

Scores higher than 99% of OCI servers

Category Cloud Infrastructure

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
  • 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 85 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 8790 tokens (~99/item across 88 items; 88 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 15 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 88 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 15 Oct 26 +1
    • Stability: 0.97 → pass security
  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 90. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 −2

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 83.

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 5 Nov 2026 · Analysed oci/ghcr.io/mp-tool/komodo-mcp-server:1.5.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via GitHub artifact attestations
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/release.yml@refs/heads/main
Rekor log index 2424259861
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:3030d0c3f5edaf2023c46856e3fc20961d3dec2d7ce5a1da0b67913397d22edd

Background: How many MCP packages publish verified provenance →

Vulnerabilities 54 ungraded findings

From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.

ID CVE Severity Vector Fix available
GHSA-f596-whhp-79r4 CVE-2026-101915 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-m9gg-hp2v-232j CVE-2026-101916 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
GHSA-jfc7-64v2-mr8c CVE-2026-48758 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L yes
GHSA-27r3-jxmh-p828 CVE-2026-111181 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3jxr-9vmj-r5cp CVE-2026-13149 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6j4f-fj2g-mc7p CVE-2026-102276 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f886-m6hf-6m8v CVE-2026-33750 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-mh99-v99m-4gvg CVE-2026-14257 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-q2hr-2g5m-vwhr CVE-2026-102277 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-qhr7-859c-m2p7 CVE-2026-102278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rgw5-rvv9-x895 CVE-2026-69152 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-333x-w4r6-6crp CVE-2026-110725 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-5jgf-p345-68v8 CVE-2026-75931 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-f65p-4m7j-42xc CVE-2026-75975 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-fph4-wmhf-6fwf CVE-2026-75899 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-hrr3-gc8f-f4qj CVE-2026-86472 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jqff-g426-hqxp CVE-2026-76172 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-qw65-cvwx-89v3 CVE-2026-84292 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-w74x-v6f9-j3xg CVE-2026-110306 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-wjr9-j795-jxcr CVE-2026-110180 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhq7-xmqj-769h CVE-2026-110095 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-3g3m-2fjr-6pw4 CVE-2026-118773 medium yes
GHSA-5r4p-p66f-jhc7 CVE-2026-109955 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-crvj-82cr-hjcx CVE-2026-84363 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-g6gw-c38x-mqfc CVE-2026-84364 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-gqvv-2mrq-wpjv CVE-2026-84365 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N yes
GHSA-hxh3-vqpv-xpqv CVE-2026-93981 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-h3mg-xc3c-68pw CVE-2026-101911 medium yes
GHSA-j6r3-76f7-8jcv CVE-2026-101912 medium yes
GHSA-mwp4-54f8-5fhr CVE-2026-69192 high yes
GHSA-rpw4-54j3-4h4q CVE-2026-101913 medium yes
GHSA-rxp7-6hxx-x8q5 CVE-2026-111997 medium yes
GHSA-v2v4-37r5-5v8g CVE-2026-42338 medium yes
GHSA-2vr4-cq9g-pvrc CVE-2026-101910 medium yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-w4pp-8pjf-rmxw CVE-2026-9496 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-3v7f-55p6-f55p CVE-2026-33672 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-c2c7-rcm5-vvqj CVE-2026-33671 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rj75-hqrm-r3gf CVE-2026-104844 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-w9m9-85wc-3x92 CVE-2026-9358 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L yes
GHSA-jqcg-44mw-7w3h CVE-2026-90711 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-4mjr-xmp4-gh2g CVE-2026-82417 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6pq8-jhm2-2vcw CVE-2026-110816 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes

Showing 50 of 54 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

MCP tools · 88 exposed · ~8,790 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
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.

NameTypeReqDescription
actionstringyesLifecycle action: 'run' executes the sync (applies pending changes — long-running, polled). 'refresh' updates the pending-changes preview without applying anything.
resource_syncstringyesResourceSync id or name
NameTypeReqDescription
actionstringyesAction name that was executed (start, stop, deploy, prune, ...)
resource_idstringyesTarget resource ID or name
resource_typestringyesTarget resource type (container, deployment, stack, server)
serverstring–Target server, when the action runs against a host
statusstringyesUpdate status reported by Komodo (Complete, InProgress, Queued, ...)
successbooleanyesWhether the action completed successfully
versionstring–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.

NameTypeReqDescription
actionstringyes'create' to register a new resource sync, 'update' to PATCH an existing one
configobject–ResourceSync configuration (repo, branch, resource_path[], file_contents, managed, etc.). Only specify fields you want to set or update.
namestring–Required when action='create' — unique name for the new resource sync
resource_syncstring–Required when action='update' — existing resource sync id or name
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_resource_sync_delete ~45

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

NameTypeReqDescription
resource_syncstringyesResourceSync id or name to delete
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_resource_sync_info ~62

Get the full Komodo ResourceSync resource including pending diffs.

NameTypeReqDescription
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
resource_syncstringyesResourceSync id or name
NameTypeReqDescription
info––Full resource sync payload, when returned inline
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–

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.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesResourceSyncs registered in Komodo
pageobject–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.

NameTypeReqDescription
actionstringyesAction to perform. Batch container ops act on every container on the host. Prune ops free disk space. Delete ops require `name`.
namestring–Required for delete_network/delete_image/delete_volume. Name of the resource to delete.
serverstringyesTarget server (id or name)
NameTypeReqDescription
actionstringyesAction name that was executed (start, stop, deploy, prune, ...)
resource_idstringyesTarget resource ID or name
resource_typestringyesTarget resource type (container, deployment, stack, server)
serverstring–Target server, when the action runs against a host
statusstringyesUpdate status reported by Komodo (Complete, InProgress, Queued, ...)
successbooleanyesWhether the action completed successfully
versionstring–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.

NameTypeReqDescription
actionstringyes'create' to register a new server, 'update' to PATCH an existing one
configobject–Server configuration fields to update (partial update)
namestring–Required when action='create' — unique name for the new server
serverstring–Required when action='update' — existing server id or name
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_server_delete ~29

Delete (unregister) a server

NameTypeReqDescription
serverstringyesServer ID or name
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_server_info ~54

Get detailed information about a specific server

NameTypeReqDescription
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
serverstringyesServer ID or name
NameTypeReqDescription
info––Full server resource payload, when returned inline
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–

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.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesServers registered in Komodo
pageobject–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.

NameTypeReqDescription
serverstringyesServer ID or name to get stats for
NameTypeReqDescription
resourceLinkobject–Reference to a server-exposed resource
serverstringyesServer ID
statusstringyesHealth status reported by Periphery

No examples provided.

komodo_stack_action ~116

Lifecycle action on a Compose stack: deploy (up), pull, start, restart, pause, unpause, stop, destroy (down — removes containers). destroy is destructive; config preserved.

NameTypeReqDescription
actionstringyesLifecycle action: deploy (compose up / re-deploy), pull (pull latest images), start (compose start), restart (stop+start), pause/unpause (freeze/resume processes), stop (compose stop), destroy (compo…
stackstringyesStack ID or name
NameTypeReqDescription
actionstringyesAction name that was executed (start, stop, deploy, prune, ...)
resource_idstringyesTarget resource ID or name
resource_typestringyesTarget resource type (container, deployment, stack, server)
serverstring–Target server, when the action runs against a host
statusstringyesUpdate status reported by Komodo (Complete, InProgress, Queued, ...)
successbooleanyesWhether the action completed successfully
versionstring–Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_stack_apply ~187

Create or update a Docker Compose stack in Komodo (PATCH-style). action="create": new stack. Required: name. Recommended: server_id (Compose) or swarm_id (Swarm). action="update": existing stack (`stack` required). Only fields in `config` change. File source on create: file_contents | repo+branch | files_on_host.

NameTypeReqDescription
actionstringyes'create' to register a new stack, 'update' to PATCH an existing one
configobject–Stack configuration fields to update (partial update)
namestring–Required when action='create' — unique name for the new stack
server_idstring–Convenience field for action='create' — target server (mirrors `config.server_id`)
stackstring–Required when action='update' — existing stack id or name
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_stack_delete ~41

Delete a Compose stack from Komodo. This removes the stack configuration but does not affect running containers.

NameTypeReqDescription
stackstringyesStack ID or name
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_stack_info ~73

Get detailed information about a Compose stack including configuration, current state, compose file contents, services, and environment variables.

NameTypeReqDescription
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
stackstringyesStack ID or name to get info for
NameTypeReqDescription
info––Full stack resource payload, when returned inline
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–

No examples provided.

komodo_stack_list ~75

List all Komodo-managed Compose stacks. Shows stack name, ID, and current state.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesStacks visible to the caller
pageobject–Pagination envelope for list responses

No examples provided.

komodo_swarm_action ~258

Swarm management. update_node: change availability/labels/role. remove_nodes: force-remove. remove_services / remove_stacks: equivalents of docker service rm / docker stack rm.

NameTypeReqDescription
actionstringyesSwarm action: update_node | remove_nodes | remove_services | remove_stacks
availabilitystring–For 'update_node': new node availability
detachboolean–For 'remove_stacks': do not wait for removal to complete
forceboolean–For 'remove_nodes': force-remove the node
label_addarray–For 'update_node': labels to add (`key=value`)
label_rmarray–For 'update_node': label keys to remove
nodestring–Required for 'update_node': node hostname or id
nodesarray–Required for 'remove_nodes': node names/ids to remove
rolestring–For 'update_node': new node role
servicesarray–Required for 'remove_services': service names/ids to remove
stacksarray–Required for 'remove_stacks': stack names to remove
swarmstringyesSwarm id or name
NameTypeReqDescription
actionstringyesAction name that was executed (start, stop, deploy, prune, ...)
resource_idstringyesTarget resource ID or name
resource_typestringyesTarget resource type (container, deployment, stack, server)
serverstring–Target server, when the action runs against a host
statusstringyesUpdate status reported by Komodo (Complete, InProgress, Queued, ...)
successbooleanyesWhether the action completed successfully
versionstring–Resulting version string, when the action produces one (e.g. deploy)

No examples provided.

komodo_swarm_apply ~152

Create or update a Komodo Swarm (PATCH-style). Servers in config.server_ids form one Docker Swarm cluster. action="create": new swarm. Required: name. Recommended: config.server_ids. action="update": existing swarm (`swarm` required). Only fields in `config` change.

NameTypeReqDescription
actionstringyes'create' to register a new swarm, 'update' to PATCH an existing one
configobject–Swarm configuration (all fields optional, PATCH-style)
namestring–Required when action='create' — unique name for the new swarm
swarmstring–Required when action='update' — existing swarm id or name
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_swarm_delete ~52

Unregister a Swarm from Komodo. Does NOT teardown the underlying Docker Swarm — it only removes the Komodo resource entry.

NameTypeReqDescription
swarmstringyesSwarm id or name to delete
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_swarm_info ~84

Get the full Komodo Swarm resource (manager server ids, links, alert/maintenance configuration). Large payloads are offloaded via a session-scoped resource link when available.

NameTypeReqDescription
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
swarmstringyesSwarm id or name
NameTypeReqDescription
info––Full Swarm resource (only when not offloaded as a resource link)
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–

No examples provided.

komodo_swarm_list ~83

List all swarms registered in Komodo. Each swarm groups one or more Server resources that act as Docker Swarm managers.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesSwarms registered in Komodo
pageobject–Pagination envelope for list responses

No examples provided.

komodo_swarm_nodes_list ~83

List the Docker nodes participating in a Komodo Swarm.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
swarmstringyesSwarm id or name
NameTypeReqDescription
itemsarrayyesNodes participating in the swarm
pageobject–Pagination envelope for list responses
swarmstringyesSwarm id or name the nodes belong to

No examples provided.

komodo_swarm_services_list ~82

List Docker services running on a Komodo Swarm.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
swarmstringyesSwarm id or name
NameTypeReqDescription
itemsarrayyesServices running on the swarm
pageobject–Pagination envelope for list responses
swarmstringyesSwarm id or name the services belong to

No examples provided.

komodo_tag_apply ~254

Create or update a Komodo Tag. Tags label resources for filtering/grouping. action="create": new tag. Required: name. Optional: color (default Slate). action="update": existing tag (`tag` required). Provide `name` to rename and/or `color` to recolor — at least one; each triggers its own API call (there is no combined update endpoint).

NameTypeReqDescription
actionstringyes'create' a new tag, or 'update' to rename/recolor an existing one
colorstring–Display color. For create: initial color (default Slate). For update: recolor the tag. Named <Shade><Base>, e.g. "Blue", "DarkRed", "LightGreen". Shade ∈ {Light, "", Dark}; Base ∈ {Slate, Red, Orange…
namestring–Required for create — the new tag name. For update, provide to rename the tag.
tagstring–Required for update — existing tag id or name
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_tag_delete ~41

Delete a Komodo Tag. Also removes this tag from every resource it was attached to.

NameTypeReqDescription
tagstringyesTag id or name to delete
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_tag_info ~45

Get the full Komodo Tag resource (id, name, owner, color). Tags are small — always returned inline.

NameTypeReqDescription
tagstringyesTag id or name
NameTypeReqDescription
tagobjectyes–

No examples provided.

komodo_tag_list ~76

List all tags registered in Komodo. Tags are labels attached to resources for filtering/grouping.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesTags registered in Komodo
pageobject–Pagination envelope for list responses

No examples provided.

komodo_toml_export_all ~210

Export every resource the caller can view as sync TOML — the same format komodo_resource_sync_* reads from a git repo. Secret values (variable values, server passkeys, alerter webhook URLs) are redacted, so the export is for inspection and diffing, not for re-applying verbatim via ResourceSync. Large output is offloaded as a session-scoped resource link unless `inline_full` is set.

NameTypeReqDescription
include_resourcesboolean–Include resources (servers, stacks, ...). Default: true
include_user_groupsboolean–Include user groups. Default: false
include_variablesboolean–Include variables. Default: false
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
tagsstring–Filter resources by tag — comma- or newline-separated names/ids (e.g. "prod, web"). Omitted = no tag filter.
NameTypeReqDescription
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–
tomlstring–The exported sync TOML (inline when small or inline_full is set)

No examples provided.

komodo_toml_export_resources ~194

Export a specific set of resources and/or user groups as sync TOML. Secret values are redacted, so the export is for inspection and diffing, not for re-applying verbatim via ResourceSync.

NameTypeReqDescription
include_variablesboolean–Include variables. Default: false
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
targetsstring–Resources to include — comma- or newline-separated "Type:id" entries, e.g. "Stack:web, Deployment:api, Server:prod-1". Type is the Komodo resource type (Server, Stack, Deployment, Build, Repo, Proced…
user_groupsstring–User groups to include — comma- or newline-separated names/ids (e.g. "admins, ops").
NameTypeReqDescription
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–
tomlstring–The exported sync TOML (inline when small or inline_full is set)

No examples provided.

komodo_update_info ~69

Get the full update payload for a single operation, including per-stage logs (stdout/stderr).

NameTypeReqDescription
idstringyesUpdate id (MongoDB ObjectId hex)
inline_fullboolean–If true, return the full payload inline instead of a compact summary. Default: false.
NameTypeReqDescription
info––Full update payload (with stage logs) when returned inline
resourceLinkobject–Reference to a server-exposed resource
summaryobjectyes–

No examples provided.

komodo_update_list ~162

List Komodo update history (audit log of operations like Deploy/RunBuild/RunSync). Newest first. Supports filtering by operation name and resource target. Pagination uses an opaque cursor string (Komodo backend is page-based).

NameTypeReqDescription
cursorstring–Opaque pagination cursor from a previous list call. Omit for the first page.
operationstring–Filter by operation name (e.g. 'Deploy', 'RunBuild')
page_sizeinteger–Maximum number of items to return (1-100)
target_idstring–Filter by resource target id
target_typestring–Filter by resource target type (e.g. 'Stack', 'Deployment', 'Build', 'Repo', 'Procedure')
NameTypeReqDescription
itemsarrayyesUpdate history items
pageobject–Pagination envelope for list responses

No examples provided.

komodo_user_create_api_key ~122

Create a new API key for the currently authenticated Komodo user. Returns the key and secret — the secret is shown only once and cannot be retrieved later. NOTE: the one-time secret is intentionally NOT redacted from this result and persists in the client transcript — rotate the key if the transcript is untrusted. Optionally set an expiry time.

NameTypeReqDescription
expires_in_daysinteger–Number of days until the key expires. 0 means no expiry. Default: 0
namestringyesA descriptive name for the API key
NameTypeReqDescription
expiresintegeryesExpiry timestamp in milliseconds since epoch (0 = never)
keystringyesAPI key ID (public identifier)
namestringyesName assigned to the new key
secretstringyesAPI key secret — shown only on creation, cannot be retrieved later

No examples provided.

komodo_user_delete_api_key ~113

Delete an API key for the currently authenticated Komodo user. Accepts either the key name or the full K_... key string. Use komodo_user_list_api_keys to see available keys.

NameTypeReqDescription
name_or_keystringyesThe key name (e.g. 'mykey') OR the full key string (e.g. 'K_abc...'). Use the name shown in komodo_user_list_api_keys. If multiple keys share the same name, provide the full K_... string.
NameTypeReqDescription
deletedbooleanyesWhether the API key was removed
key_idstringyesThe full K_... key string that was deleted
namestring–The key name, when resolved by name lookup

No examples provided.

komodo_user_list_api_keys ~87

List all API keys for the currently authenticated Komodo user. Shows key name, key ID (not secret), creation date, and expiry.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesAPI keys for the authenticated user
pageobject–Pagination envelope for list responses

No examples provided.

komodo_variable_apply ~162

Create or update a Komodo Variable (PATCH-style on update). action="create": new variable. Required: name. Optional: value, description, is_secret. action="update": existing variable (name required). Each of value, description, is_secret triggers a separate update call when provided.

NameTypeReqDescription
actionstringyes'create' to register a new variable, 'update' to change an existing variable's value/description/is_secret
descriptionstring–Optional description
is_secretboolean–If true, mark the variable as a secret (value redacted in responses)
namestringyesVariable name (unique key)
valuestring–Variable value — required for action='create'; optional for update
NameTypeReqDescription
actionstringyesWhich apply action was performed
resourceobject–Full resource returned by Komodo (when available)
resource_idstringyesResource id or name affected
resource_typestringyesTarget resource type

No examples provided.

komodo_variable_delete ~48

Delete a Komodo Variable. Stacks/Deployments referencing it via `[[variable.name]]` will fail to interpolate afterwards.

NameTypeReqDescription
namestringyesVariable name (unique key)
NameTypeReqDescription
actionstringyesAlways 'remove' for delete tools
resourceobject–Snapshot of the deleted resource (when available)
resource_idstringyesResource id or name that was removed
resource_typestringyesTarget resource type

No examples provided.

komodo_variable_info ~39

Get a single Komodo variable. Secret variables are redacted for non-admin users.

NameTypeReqDescription
namestringyesVariable name (unique key)
NameTypeReqDescription
variableobjectyes–

No examples provided.

komodo_variable_list ~78

List all global variables registered in Komodo. Secret variables have their value redacted for non-admin users.

NameTypeReqDescription
cursorstring–Opaque pagination cursor returned by a previous list call. Omit for the first page.
page_sizeinteger–Maximum number of items to return (1-100). Default: 25.
NameTypeReqDescription
itemsarrayyesVariables registered in Komodo
pageobject–Pagination envelope for list responses

No examples provided.

Install

How do I install the Komodo MCP Server server?

Komodo MCP Server runs locally as a container image, launched with docker run --rm -i -e KOMODO_URL -e KOMODO_API_KEY -e KOMODO_API_SECRET -e KOMODO_USERNAME -e KOMODO_PASSWORD ghcr.io/mp-tool/komodo-mcp-server:1.5.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mp-tool/komodo-mcp-server:1.5.0

# add to Claude Code
claude mcp add mp-tool-komodo-mcp-server -- docker run --rm -i -e KOMODO_URL -e KOMODO_API_KEY -e KOMODO_API_SECRET -e KOMODO_USERNAME -e KOMODO_PASSWORD ghcr.io/mp-tool/komodo-mcp-server:1.5.0

This image reads KOMODO_URL, KOMODO_API_KEY, KOMODO_API_SECRET, KOMODO_USERNAME and KOMODO_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Komodo MCP Server server?

Komodo MCP Server is listed in the public MCP registry as io.github.MP-Tool/komodo-mcp-server. MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI. This page covers its container image (ghcr.io/mp-tool/komodo-mcp-server:1.5.0).

Is the Komodo MCP Server server safe to use?

Komodo MCP Server scores 67 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 54 known advisories as of 5 November 2026. We do not grade that SBOM, as nothing verifies it. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Komodo MCP Server server expose?

Komodo MCP Server exposes 88 tools: komodo_health_check, komodo_container_list, komodo_container_inspect, komodo_container_logs, komodo_container_search_logs, and 83 more. Their descriptions and schemas cost roughly 8,790 tokens of context every time the server is loaded.

Is the Komodo MCP Server server still maintained?

Komodo MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Komodo MCP Server server under?

Komodo MCP Server declares the GPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.