Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OS_CACERTNoSSL CA certificate path for HTTPS (optional, required for secure HTTPS if using https)
OS_PASSWORDYesOpenStack password (required)
OS_USERNAMEYesOpenStack username (required)
FASTMCP_HOSTNoHTTP host address for streamable-http mode127.0.0.1
FASTMCP_PORTNoHTTP port for streamable-http mode8080
FASTMCP_TYPENoTransport type (stdio, streamable-http)stdio
OS_AUTH_HOSTYesOpenStack Identity service host address (required)
OS_AUTH_PORTYesOpenStack Identity service port (required)
OS_INTERFACENoInterface type (public, internal, admin)public
MCP_LOG_LEVELNoLogging level (DEBUG, INFO, WARNING, ERROR, CRITICAL)INFO
OS_IMAGE_PORTNoImage service port9292
OS_REGION_NAMENoOpenStack region nameRegionOne
OS_VOLUME_PORTNoVolume service port8776
OS_COMPUTE_PORTNoCompute service port8774
OS_NETWORK_PORTNoNetwork service port9696
OS_PROJECT_NAMEYesOpenStack project name (required)
OS_AUTH_PROTOCOLNoConnection protocol (http or https)http
OS_PLACEMENT_PORTNoPlacement service port8780
REMOTE_SECRET_KEYNoSecret key for Bearer token authentication (required if REMOTE_AUTH_ENABLE=true)
OS_HEAT_STACK_PORTNoHeat orchestration service port8004
REMOTE_AUTH_ENABLENoEnable Bearer token authentication for streamable-http modefalse
OS_USER_DOMAIN_NAMENoUser domain namedefault
OS_HEAT_STACK_CFN_PORTNoHeat CloudFormation service port18888
OS_PROJECT_DOMAIN_NAMENoProject domain namedefault
ALLOW_MODIFY_OPERATIONSNoEnable modify operations (true/false)false
OS_IDENTITY_API_VERSIONNoIdentity API version3

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

MCP-OpenStack-Ops operates one OpenStack project through real OpenStack API calls: compute, networking, block storage, images, identity, Heat, Octavia load balancers, Barbican secrets, quotas, Gnocchi telemetry, and Aodh alarms.

Scope and availability

  • Every tool call is a real API request scoped to the configured project (OS_PROJECT_NAME). Use the tools for facts; never guess, simulate, or invent results.

  • set_* tools exist only when the server sets ALLOW_MODIFY_OPERATIONS=true. If a needed set_* tool is missing, say that modifications are disabled.

  • Some read tools accept all_projects=true, which works only when the server sets ALLOW_CROSS_PROJECT_READ=true. Use it only when the user asks about all or other projects, group results by project_name, and mention scope.warning when present. Report a disabled-switch or policy-denial error as-is; never present current-project results as cloud-wide. Modifications and lookups by name stay in the current project, except get_project_details with all_projects=true, which accepts another project's name or ID.

  • Optional services (Octavia, Barbican, Heat, Gnocchi, Aodh, port forwarding) may be absent from the cloud. Report the returned error; do not claim the feature works.

Reporting results

  • Report what the tool returned. Never claim success after an error, an empty response, a partial result, or reported failures; quote the error.

  • Many operations are asynchronous: an accepted request is not a completed one. Say so, and confirm the final state with a read tool when it matters.

Changing resources

  • Confirm destructive actions (delete, stop, rebuild, detach) with the user before running them.

  • When the user targets resources by pattern ("all test instances") for a destructive action, list the matches with a read tool first. set_* tools accept comma-separated names, a JSON array, or filters such as name_contains.

  • If required creation parameters are missing (for example flavor, image or boot volume, network, size, CIDR), ask for them instead of attempting the operation.

  • To open a port, ask for the source CIDR or remote group; never assume 0.0.0.0/0 or ::/0.

  • Never ask for passwords in chat. set_users reads a password from the server environment variable named by password_env.

  • Never ask for or accept private keys, certificates, or other secret payloads in chat; no tool takes or returns them. Users register their own certificates in Barbican outside MCP; refer to them by name or href.

Numbers and monitoring

  • Allocation, quota, and capacity (get_resource_monitoring, get_quota, get_hypervisor_details, get_usage_statistics) are not measured utilization. Measured values come only from Gnocchi (get_gnocchi_measures, get_gnocchi_aggregates).

  • Label every number as allocated, quota, capacity, or measured. Never divide project allocations by physical capacity. Missing capacity is null, not zero. If a metric is not collected, say "not collected"; never estimate it.

  • Gnocchi metrics vcpus, memory, and disk.root.size record flavor sizes, not usage.

Large projects

  • Instance and load balancer listings paginate (50 per request by default, at most the server's LIST_MAX_LIMIT). Use limit and offset; use include_all only when the user needs every item.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_availability_zonesB

List availability zones and their status

get_domainsB

List Keystone domains subject to cloud policy.

get_floating_ip_poolsA

Get list of floating IP pools (external networks).

Functions:

  • List all external networks that can provide floating IPs

  • Show available and used IP counts for each pool

  • Display network configuration for floating IP allocation

  • Provide pool capacity and utilization information

Use when user requests:

  • "Show floating IP pools"

  • "List available floating IP networks"

  • "Check floating IP capacity"

  • "What external networks are available?"

get_floating_ipsB

Get list of floating IPs with their associations.

Functions:

  • Query floating IPs and their current status

  • Display associated fixed IPs and ports

  • Show floating IP pool and router associations

  • Provide floating IP allocation and usage information

Use when user requests floating IP information, external connectivity queries, or IP management tasks.

get_gnocchi_aggregatesA

Aggregate measured telemetry across many current-project resources.

Use for cross-resource questions: project-wide averages or totals, top N resources, per-flavor or per-host groups, and ratios between metrics. For one resource's time series, use get_gnocchi_measures instead. For allocations, capacity, or quotas, use get_resource_monitoring.

Choose ONE mode:

  1. Simple mode (preferred): set metric and aggregation, plus optional reaggregation, groupby, and top. Leave operations empty.

    • Project-wide average CPU: metric="cpu", aggregation="rate:mean", reaggregation="mean"

    • Top 5 instances by CPU: metric="cpu", aggregation="rate:mean", top=5

    • Mean memory use per flavor: metric="memory.usage", reaggregation="mean", groupby="flavor_name"

  2. Expression mode: set operations only, for arithmetic between metrics or advanced Gnocchi functions. Leave metric and reaggregation empty. Write metric NAMES, never metric UUIDs, as (metric NAME AGGREGATION). Example ratio: (/ (metric memory.usage mean) (metric memory mean)) Arithmetic returns points only where every operand has data; memory (flavor size) is recorded sparsely, so this ratio has fewer points.

Units: cpu with rate:mean is CPU nanoseconds per granularity window; utilization fraction = value / (granularity * 1e9 * vCPUs). memory.usage is MB in use. vcpus and memory are flavor sizes, not usage.

Results are always limited to resources of the current project. The response echoes the executed operations expression.

get_gnocchi_measuresA

Read stored Gnocchi measures (telemetry time series) for a metric.

Use for measured utilization, load, trends, and history ("CPU usage of vm1", "memory over the last hour"). Values are observed telemetry collected by Ceilometer, such as cpu, memory.usage, or disk and network counters. Cumulative counters like cpu (nanoseconds) grow over time; compare consecutive values for rates. Some metrics such as vcpus and memory record flavor sizes, not usage. For averages, totals, top N, or groups across many resources, use get_gnocchi_aggregates. For allocations, capacity, or quotas, use get_resource_monitoring or get_quota. If a metric is not collected, report that; do not substitute allocation data.

get_gnocchi_metricsA

List or show current-project Gnocchi metrics.

Without arguments, lists metric names and IDs of current-project resources. With resource_id, shows that resource's metrics including archive policy and unit. With metric, shows one metric. Use it to check which telemetry metrics are actually collected before reading measures or creating alarms. These are measured telemetry series, not allocations or quotas.

get_gnocchi_resourcesA

List, search, or show current-project Gnocchi (telemetry) resources.

Resources are the objects Ceilometer measures, such as instances, disks, and network interfaces. Each resource maps metric names to metric IDs. Use this to find which metrics exist for a server before reading measures.

get_gnocchi_service_infoA

Read Gnocchi service configuration and health information.

Use to check which granularities and aggregation methods a metric supports (for get_gnocchi_measures or set_alarms), which resource types exist, and whether measure processing is backlogged.

get_heat_stack_detailsB

Query resources, events, template, or outputs for a Heat stack.

get_heat_stacksA

Get list of Heat orchestration stacks.

Functions:

  • Query Heat stacks and their current status

  • Display stack creation and update timestamps

  • Use get_heat_stack_details for templates, resources, events, or outputs

  • Provide orchestration deployment information

Use when user requests stack information, orchestration queries, or infrastructure-as-code status.

get_hypervisor_detailsC

Get detailed information about hypervisors

get_identity_groupsC

List Keystone groups subject to cloud policy.

get_image_detail_listB

Get detailed list of all images with comprehensive metadata.

Functions:

  • List all images available in the project

  • Show image status, size, and format information

  • Display image properties and metadata

  • Provide ownership and visibility details

Use when user requests image listing, image information, or image metadata details.

get_image_membersC

List member projects for an image.

get_instanceA

Unified instance query tool supporting all instance retrieval patterns. Consolidates functionality from get_instance_details, get_instance_by_name, get_instances_by_status, and search_instances.

Functions:

  • Get specific instances by names or IDs

  • Filter instances by status (ACTIVE, SHUTOFF, ERROR, etc.)

  • Search instances across multiple fields (name, flavor, image, host, etc.)

  • List all instances with pagination

  • Support both summary and detailed information modes

Use when user requests instance information, status checks, or instance searches.

get_instance_by_nameB

Get detailed information for a specific instance by name.

get_instance_detailsB

Provides detailed information and status for OpenStack instances with pagination support.

Functions:

  • Query basic instance information (name, ID, status, image, flavor) with efficient pagination

  • Collect network connection status and IP address information

  • Check CPU, memory, storage resource usage and allocation

  • Provide instance metadata, keypair, and security group settings

  • Support large-scale environments with configurable limits

Use when user requests specific instance information, VM details, server analysis, or instance troubleshooting.

get_instances_by_statusC

Get instances filtered by status.

get_key_manager_quotasA

Show the effective Barbican quotas (secrets, orders, containers, consumers, CAs) of the current project; -1 means unlimited.

get_keypair_listA

Get list of SSH keypairs for the current user.

Functions:

  • Query SSH keypairs and their fingerprints

  • Display keypair types and creation dates

  • Show public key information (truncated for security)

  • Provide keypair management information

Use when user requests SSH key management, keypair information, or security key queries.

get_load_balancer_amphoraeA

Get amphora instances for a load balancer or all amphorae.

get_load_balancer_availability_zonesC

Get load balancer availability zones.

get_load_balancer_detailsA

Get detailed information about a specific OpenStack load balancer.

Functions:

  • Shows comprehensive load balancer details including VIP configuration

  • Lists all listeners with their protocols and ports

  • Shows pools and members for each listener

  • Displays health monitor information if configured

  • Provides provisioning and operating status

Use when user requests:

  • "Show details for load balancer [name/id]"

  • "Get load balancer configuration"

  • "Show load balancer listeners and pools"

  • "What's the status of load balancer [name]?"

get_load_balancer_flavorsC

Get load balancer flavors.

get_load_balancer_health_monitorsA

Get health monitors, optionally filtered by pool.

Functions:

  • Lists all health monitors or monitors for a specific pool

  • Shows monitor types (HTTP, HTTPS, TCP, PING, UDP-CONNECT)

  • Displays health check intervals, timeouts, and retry settings

  • Provides HTTP-specific settings (method, URL path, expected codes)

Use when user requests:

  • "Show all health monitors"

  • "List health monitors for pool [name/id]"

  • "What health checks are configured?"

  • "Show health monitor configuration"

get_load_balancer_l7_policiesA

Get L7 policies for a listener or all L7 policies.

get_load_balancer_l7_rulesC

Get L7 rules for a specific L7 policy.

get_load_balancer_listA

Retrieve comprehensive list of OpenStack load balancers with detailed information.

Functions:

  • Lists all load balancers in the OpenStack cluster

  • Provides detailed load balancer information including VIP, status, listeners

  • Supports pagination for large environments (limit/offset)

  • Shows listener count and basic listener information for each load balancer

  • Displays provisioning and operating status for troubleshooting

Use when user requests:

  • "Show me all load balancers"

  • "List load balancers with details"

  • "What load balancers are available?"

  • "Show load balancer status"

get_load_balancer_listenersA

Get listeners for a specific OpenStack load balancer.

Functions:

  • Lists all listeners attached to a load balancer

  • Shows listener protocols, ports, and configurations

  • Displays admin state and default pool associations

  • Provides creation and update timestamps

Use when user requests:

  • "Show listeners for load balancer [name/id]"

  • "List load balancer listeners"

  • "What ports are configured on load balancer [name]?"

  • "Show listener configuration for [lb_name]"

get_load_balancer_pool_membersA

Get members for a specific OpenStack load balancer pool.

Functions:

  • Lists all members in a specific pool

  • Shows member addresses, ports, weights, and health status

  • Displays member admin state and operational status

  • Provides monitor configuration for each member

Use when user requests:

  • "Show members for pool [name/id]"

  • "List pool members"

  • "What members are in pool [name]?"

  • "Show pool member status"

get_load_balancer_poolsA

Get load balancer pools, optionally filtered by listener.

Functions:

  • Lists all pools or pools for a specific listener

  • Shows pool protocols, load balancing algorithms

  • Displays members in each pool with their status

  • Provides health monitor associations

Use when user requests:

  • "Show all load balancer pools"

  • "List pools for listener [name/id]"

  • "What pools are configured on [listener_name]?"

  • "Show pool members and their status"

get_load_balancer_providersC

Get load balancer providers.

get_load_balancer_quotasA

Get load balancer quotas for a project or all projects.

get_network_detailsA

Provides detailed information for OpenStack networks, subnets, routers, and security groups.

Functions:

  • Query configuration information for specified network or all networks

  • Check subnet configuration and IP allocation status per network

  • Collect router connection status and gateway configuration

  • Analyze security group rules and port information

Use when user requests network information, subnet details, router configuration, or network troubleshooting.

get_network_qos_policiesA

List project-owned Neutron QoS policy containers; no bandwidth rules are created.

get_project_detailsC

Get OpenStack project details (similar to 'openstack project list/show').

get_quotaA

Get quota information for projects (similar to 'openstack quota show').

Each service reports limits, usage and usage_percent (percent of each limit in use). A usage value is null when it could not be determined, and usage_percent is null for unlimited (-1), zero or missing limits and for unknown usage.

get_resource_monitoringA

Read current project allocations and visible hypervisor capacity.

Functions:

  • Report project flavor allocations, not live CPU or memory utilization

  • Collect hypervisor statistics and resource allocation

  • Separate project quota limits from visible physical capacity

  • Return null for unavailable capacity or incomplete flavor allocations

Use for current inventory and capacity planning. No historical trends or telemetry samples are collected. Physical totals and project allocations have different scopes and should not be divided into a utilization rate. For measured CPU/memory utilization, load, or trends, use get_gnocchi_measures instead; never present these allocations as usage.

get_role_assignmentsA

Get role assignments for the current project.

Functions:

  • Query role assignments for users and groups

  • Display project-level and domain-level permissions

  • Show scope of role assignments

  • Provide comprehensive access control information

Use when user requests permission information, access control queries, or security auditing.

get_routersB

Get list of routers with their configuration.

Functions:

  • Query routers and their external gateway configurations

  • Display router interfaces and connected networks

  • Show routing table entries and static routes

  • Provide comprehensive network routing information

Use when user requests router information, network connectivity queries, or routing configuration.

get_secret_aclA

Show the read ACL of a Barbican secret or container.

The ACL lists users outside the owning project allowed to read it and whether project-wide access (project-access) is enabled.

get_secret_containersB

List or show Barbican secret containers of the current project.

A container groups secret hrefs, e.g. a certificate container with certificate, private_key and intermediates entries. Payloads are never returned.

get_secret_ordersA

List or show Barbican key-generation orders of the current project.

An ACTIVE order points to the generated secret (key orders) or container (asymmetric orders) through secret_ref or container_ref.

get_secret_storesA

List Barbican secret store backends. Only clouds that enable multiple secret store backends serve this API; others return an error.

get_secretsA

List or show Barbican secrets of the current project (metadata only).

Never returns a secret payload; payload retrieval is intentionally not provided so key material cannot reach the LLM. Use the secret_ref from this tool as a reference, for example in set_load_balancer_listener.

get_security_groupsA

Get list of security groups with their rules.

Functions:

  • Query security groups and their rule configurations

  • Display ingress and egress rules with protocols and ports

  • Show remote IP prefixes and security group references

  • Provide comprehensive network security information

Use when user requests security group information, firewall rules, or network security queries.

get_server_eventsA

Get recent events for a server by name or UUID.

Pass either value using instance_name, for example get_server_events(instance_name=""). There is no server_id parameter; do not use server_id or instance_id as argument names.

get_server_groupsC

List all server groups with their details

get_server_volumesC

Get all volumes attached to a specific server

get_service_statusA

Provides status and health check information for each OpenStack service.

Functions:

  • Check active status of all OpenStack services

  • Verify API endpoint responsiveness for each service

  • Collect detailed status and version information per service

  • Detect and report service failures or error conditions

Use when user requests service status, API status, health checks, or service troubleshooting.

get_usage_statisticsA

Get current-project Nova allocation-hours and separate current snapshots.

Functions:

  • Show project usage statistics over a specified time period

  • Display servers, RAM MB-Hours, CPU Hours, and Disk GB-Hours

  • Provide detailed server usage breakdown when available

  • Keep current compute/network/storage snapshots separate from period data

Use for project usage reports. Period data comes from Nova simple tenant usage. It measures allocation-hours, not live utilization or monetary charges. For measured CPU/memory utilization or trends, use get_gnocchi_measures. Missing or denied usage API returns failure without synthetic fallback.

get_user_listA

Get list of OpenStack users in the current domain.

Functions:

  • Query user accounts and their basic information

  • Display user status (enabled/disabled)

  • Show user email and domain information

  • Provide user creation and modification timestamps

Use when user requests user management information, identity queries, or user administration tasks.

get_volume_backupsB

List Cinder backups visible in the current project.

get_volume_groupsA

List current-project Cinder generic groups. Requires API microversion >= 3.13.

get_volume_listA

Get list of all volumes with detailed information.

Functions:

  • List all volumes in the project

  • Show volume status, size, and type information

  • Display attachment information for volumes

  • Provide detailed metadata for each volume

Use when user requests volume listing, volume information, or storage overview.

get_volume_qosA

List Cinder QoS specifications, or show one specification's volume type associations by name or ID. Cloud policy may require admin rights.

get_volume_snapshotsA

Get list of volume snapshots.

Functions:

  • Query volume snapshots and their status

  • Display source volume information

  • Show snapshot creation and modification dates

  • Provide snapshot size and usage information

Use when user requests snapshot information, backup queries, or volume restoration planning.

get_volume_transfersA

List current-project Cinder volume transfer requests without authorization keys.

get_volume_typesA

Get list of volume types with their specifications.

Functions:

  • Query volume types and their capabilities

  • Display extra specifications and backend configurations

  • Show public/private volume type settings

  • Provide storage backend information

Use when user requests volume type information, storage backend queries, or volume creation planning.

search_instancesB

Search for OpenStack instances based on various criteria with efficient pagination.

Functions:

  • Search instances by name, status, host, flavor, image, or availability zone

  • Support partial matching with configurable case sensitivity

  • Return detailed information for matching instances with pagination

  • Optimized for large-scale environments with intelligent filtering

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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