Ocm Mcp Server

io.github.sandeepbazarPublished by GitHub account sandeepbazarv0.4.0Updated Oct 24, 2026

Guardrailed fleet ops for AI agents: multi-cluster Kubernetes via OCM with policy, approval, audit.

VerifiedSTDIODesktop onlyCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Guardrailed fleet operations for AI assistants: multi-cluster Kubernetes management through OCM, with policy, approval and audit controls.

What you can do
Manage multi-cluster Kubernetes fleets through OCM, using the kubeconfig contexts for the hub and optional spoke clusters. Operate under guardrails: policy checks, an approval step and audit of actions. Restrict access to read-only fleet visibility when the write path is disabled.
When to use it
Worth adding when an assistant needs to inspect or operate several Kubernetes clusters registered with an OCM hub, and you want policy, approval and audit around any changes rather than direct cluster access.
Requirements
Runs locally over stdio, from the PyPI package with uvx or the container image with Docker. Needs a kubeconfig file whose path is given in KUBECONFIG, containing the OCM hub context and optional spoke contexts. OCM_MCP_HUB_CONTEXT selects the hub context (defaults to the current one); OCM_MCP_READ_ONLY set to 'true' disables the write path.
Before you install
The server can act on real clusters, so changes may affect workloads across the fleet; keep OCM_MCP_READ_ONLY set to 'true' unless writes are intended. The kubeconfig referenced by KUBECONFIG typically holds cluster credentials and should be scoped to the least privilege needed. Review the policy and approval behavior before enabling the write path.

Installation

In SourceWeft

  1. Open Ocm Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.