Skip to main content
Glama
badin017

ocp-mcp

by badin017
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ocp-mcp

No user-submitted related servers found.

    Related Servers

    • RHOAI MCP Server

      opendatahub-io
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to interact with Red Hat OpenShift AI environments, providing tools for project management, workbench operations, model serving, and more.
      239 PyPI
      9
      MIT

    • openshift-mcp

      LesterAJohn
      A
      license
      C
      quality
      B
      maintenance
      An MCP server for managing OpenShift clusters and querying Amazon Redshift across multiple clusters, with secure secret and configuration persistence.
      43
      MIT

    • Multi Cluster Kubernetes MCP

      feibai406
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables interaction with multiple Kubernetes clusters simultaneously, providing comprehensive tools for cluster management, resource operations, and diagnostics across different environments.
      -

    • k8s-mcp-server

      Tobewont
      A
      license
      C
      quality
      B
      maintenance
      An MCP server that provides complete Kubernetes API operations, enabling cluster management, resource CRUD, diagnostics, backup/restore, and multi-cluster configuration via natural language.
      32
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 77 tools

    Disambiguation4/5

    Most tools target distinct resource types (list_* vs get_* per kind), and overlap is limited to a few areas like logs (get_pod_logs, get_all_container_logs, get_previous_pod_logs) and deployment operations (rollout_restart, rollback_deployment, get_deployment_revision_history). Descriptions clarify these related tools, so an agent can usually pick the right one, but the sheer number increases selection risk.

    Naming Consistency4/5

    The dominant pattern is verb_noun in snake_case (list_pods, get_deployment, scale_statefulset), which is predictable. However, there are deviations like rollout_restart (noun_verb), top_pods/top_nodes (no list/get prefix), and pod_resource_usage_vs_requests (descriptive phrase) that break the strict pattern.

    Tool Count2/5

    With 77 tools, the surface is very large and far exceeds the typical well-scoped range. While OpenShift is broad, many tools are similar list/get variants for different resource kinds, making the server feel overloaded. This volume could overwhelm agents and increase decision cost.

    Completeness3/5

    The server covers a wide range of OpenShift resources with list/get, scaling, logs, events, and monitoring. However, there are notable gaps: no create/update for most resources, delete only for a few kinds, and missing some common resources like roles/rolebindings. Core operational workflows are present, but full lifecycle coverage is incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources