Ocm MCP Server

What the code does

We have not read this server's code yet, 29 d ago · rules ccca72095570

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    inj = subprocess.run(["bash", f"{root}/chaos/inject.sh", "failing-rollout", cl],

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

этот файл ставится пользователю, но в репозитории его нет

    return subprocess.run(

        cmd, shell=True, capture_output=True, text=True, timeout=timeout, check=False

        path = os.path.join(REPO, rel_path)

            env=dict(os.environ),

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add ocm-mcp-server -e 'KUBECONFIG=<KUBECONFIG>' -- uvx ocm-mcp-server

{
  "mcpServers": {
    "ocm-mcp-server": {
      "command": "uvx",
      "args": [
        "ocm-mcp-server"
      ],
      "env": {
        "KUBECONFIG": "<KUBECONFIG>"
      }
    }
  }
}

[mcp_servers.ocm-mcp-server]
command = "uvx"
args = ["ocm-mcp-server"]
env = { KUBECONFIG = "<KUBECONFIG>" }

{
  "mcpServers": {
    "ocm-mcp-server": {
      "command": "uvx",
      "args": [
        "ocm-mcp-server"
      ],
      "env": {
        "KUBECONFIG": "<KUBECONFIG>"
      }
    }
  }
}

{
  "servers": {
    "ocm-mcp-server": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ocm-mcp-server"
      ],
      "env": {
        "KUBECONFIG": "<KUBECONFIG>"
      }
    }
  }
}

Put your own value in place of <KUBECONFIG> (Path to the kubeconfig with the OCM hub context (and optional spoke contexts)). The author’s registry entry marks it as required.

Optional settings from the registry entry, left out of the block above: OCM_MCP_HUB_CONTEXT (Kubeconfig context name of the OCM hub cluster (defaults to the current context)), OCM_MCP_READ_ONLY (Set to 'true' to disable the gated write path entirely (read-only fleet access)).