clusters

MCP tool from Ocm MCP Server by sandeepbazar

(string, optional) - comma-separated cluster names to scope the sweep; empty means every cluster.

How to use it

clusters is exposed by the Ocm MCP Server MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the clusters tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.

Install Ocm MCP Server

$docker run -d --name jaeger -p 16686:16686 -p 4318:4318 jaegertracing/all-in-one:1.60

FULL OCM MCP SERVER LISTING

Other tools in Ocm MCP Server (15)

action

(string) - one of cordon (taint out of scheduling), uncordon, setlabel, accept (hubAcceptsClient + approve join CSRs), enableaddon / disableaddon (create/delete a ManagedClusterAddOn).

cluster

(string) - managed cluster name.

container

(string, optional) - container name; empty picks the default.

last_n

(int, optional) - trailing entries (default 30).

limit

(int, optional) - max events (default 40).

lines

(int, optional) - trailing lines (default 80).

manifests_json

(string) - JSON array of complete manifests (allowed kinds; namespaced; pinned images).

name

(string) - short kebab-case ManifestWork name.

namespace

(string, optional) - limit to one namespace; empty lists all.

params_json

(string, optional) - action parameters; setlabel needs {"key","value"}, the add-on actions need {"addon"} (+ optional installnamespace).

placement

(string) - Placement name.

proposal_id

(string), approvaltoken (string) - from ocm-mcp approve <id>.

resource

(string) - e.g. managedclusters, placements, manifestworks, managedclusteraddons, klusterlets.

rollback_proposal_id

(string), approvaltoken (string).

summary

(string) - one or two sentences the human approver reads.