Skip to main content
Glama
call518

MCP-OpenStack-Ops

by call518
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MCP-OpenStack-Ops

No user-submitted related servers found.

    Related Servers

    • proxmox-mcp

      plgonzalezrx8
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for Proxmox VE that enables read-only cluster inspection, VM/container lifecycle operations, snapshots, migration, and provisioning with safe confirmation gates.
      28
      MIT

    • MCP Store

      Meir83
      A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server for IT, DBA, and developer tasks, enabling error resolution, task automation, performance monitoring, automated documentation, and configuration management.
      2 npm
      ISC

    • 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.
      -
    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.2/5.0

    Scored across 41 tools

    Disambiguation2/5

    The instance-retrieval surface is highly overlapping: get_instance claims to consolidate get_instance_details, get_instance_by_name, get_instances_by_status, and search_instances, yet all five remain exposed, making misselection very likely. get_network_details also overlaps with get_routers and get_security_groups, and some load balancer list/detail tools are close enough to confuse without careful reading.

    Naming Consistency5/5

    Tool names consistently follow snake_case verb_noun conventions, overwhelmingly using get_* prefixes with predictable resource names. search_instances is a slight verb variation but still fits the same predictable pattern and style.

    Tool Count2/5

    With 41 tools, the surface is well above the recommended range for a single MCP server and feels heavy even for a broad domain like OpenStack. The large count is compounded by redundant instance and network tools that could be consolidated into fewer well-scoped tools.

    Completeness3/5

    Read-only coverage is broad across compute, storage, networking, identity, load balancing, orchestration, images, and quotas. However, there are no lifecycle or action tools for creating, updating, deleting, starting/stopping, attaching, or detaching resources, which are notable gaps for an OpenStack operations server.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources