Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Related Servers

Alternatives to MCP-OpenStack-Ops

No user-submitted related servers found.

    Related Servers

    • 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
    • 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.
      6 npm
      ISC
    • 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.
      -

    TDQS

    C2.8/5.0

    Scored across 61 tools

    Disambiguation2/5

    The instance tools overlap heavily: get_instance is explicitly a unified replacement for get_instance_details, get_instance_by_name, get_instances_by_status, and search_instances, yet all of those legacy tools remain exposed. Other areas are better separated, but the retained redundant instance tools create multiple unclear boundaries for an agent.

    Naming Consistency4/5

    Almost all tools use a predictable get_snake_case pattern, with consistent resource grouping such as get_load_balancer_* and get_volume_*. The main deviation is search_instances, and some names awkwardly append list/detail/list, but overall naming is readable and mostly consistent.

    Tool Count1/5

    With 61 tools, the surface is far beyond the typical well-scoped range and well into the 50+ extreme-mismatch category. Granular read-only queries for load balancer subresources, Gnocchi telemetry, Barbican secrets, and many OpenStack services make the toolset unwieldy for an agent.

    Completeness1/5

    The tool surface is almost entirely read-only get/search operations, with no create, update, delete, or lifecycle action tools for instances, networks, volumes, load balancers, Heat stacks, secrets, keypairs, or users. For an OpenStack ops server, this is a severe gap that prevents most operational workflows.

    Maintenance

    ActivityActive
    ResponsivenessLimited data