get_availability_zones
List availability zones and their status
Returns: JSON string with availability zones information
LABSCO SUMMARY
Read-only by default and scoped to one project, which is the right shape for letting an agent near a cloud tenant.
The safety model is not a warning in the README — modifying tools are not registered at all unless the flag is set, and every call checks the resource against the configured project. The coverage is unusually deep on Octavia: listeners, pools, members, health monitors and L7 rules are separate reads, which is what a load-balancer problem actually needs.
What it is
An operations server scoped to a single OpenStack project: every tool validates that the resource belongs to the configured project, and modifying tools are not even registered until you enable them.
What you get
- Compute visibility at several grains: instances listed, found by name, filtered by status, searched, and read in detail with their events, volumes and server groups
- Networking read back — network details, routers, security groups, floating IPs and the pools they come from, and availability zones
- Storage: volumes with their types and snapshots, and which volumes are attached to a given server
- Images listed with their details, and keypairs
- Octavia load balancing in depth — balancers with their details, listeners, pools and members, health monitors, L7 policies and rules, amphorae, flavors, providers, quotas and availability zones
- Heat stacks for the project
- Capacity and identity context: quotas, usage statistics, resource monitoring, hypervisor details, service status, project details, the user list and role assignments
- Bulk and filtered operations, with comma-delimited lists accepted where you would otherwise call the same tool repeatedly
Requirements
OpenStack credentials in the standard variables — OS_AUTH_HOST and OS_AUTH_PORT with OS_AUTH_PROTOCOL, OS_IDENTITY_API_VERSION, OS_USERNAME, OS_PASSWORD, OS_PROJECT_NAME with its domain names and OS_REGION_NAME, plus OS_CACERT when you run it over HTTPS. Service ports are configurable per service. Published on PyPI as mcp-openstack-ops, with a Docker image and compose setup as an alternative. Writes stay off until ALLOW_MODIFY_OPERATIONS is set to true, at which point the modifying tools appear.
Setup effort
One command plus credentials — uvx mcp-openstack-ops, then supply credentials
USE CASES
01
Finding out what state an instance is in
Look it up by name, read its details, then its events and attached volumes.
02
Working out why traffic is not reaching a service
Read the load balancer, then its listeners, pools, members and health monitors.
03
Chasing a connectivity problem
Check the security groups, the network details and the routers, and confirm the floating IP is where you think it is.
04
Seeing whether you are about to run out of room
Read the project's quotas against its usage statistics and current resource monitoring.
05
Taking stock before a change
List the instances by status, the volumes and their snapshots, and the images available.
06
Checking the cloud itself, not your workload
Read service status, hypervisor details and availability zones.
41 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_floating_ip_pools
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?"
Returns: List of floating IP pools with capacity information in JSON format.
get_floating_ips
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.
Returns: List of floating IPs with detailed association information in JSON format.
get_heat_stacks
Get list of Heat orchestration stacks.
Functions:
- Query Heat stacks and their current status
- Display stack creation and update timestamps
- Show stack templates and resource information
- Provide orchestration deployment information
Use when user requests stack information, orchestration queries, or infrastructure-as-code status.
Returns: List of Heat stacks with detailed information in JSON format.
get_hypervisor_details
Get detailed information about hypervisors
get_image_detail_list
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.
Returns: Comprehensive image list in JSON format with detailed metadata, properties, and status information.
get_instance
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_name
Get detailed information for a specific instance by name.
get_instance_details
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_status
Get instances filtered by status.
get_keypair_list
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.
Returns: List of SSH keypairs with detailed information in JSON format.
get_load_balancer_amphorae
Get amphora instances for a load balancer or all amphorae.
get_load_balancer_availability_zones
Get load balancer availability zones.
Returns: JSON string containing availability zones information
get_load_balancer_details
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_flavors
Get load balancer flavors.
Returns: JSON string containing flavors information
get_load_balancer_health_monitors
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_policies
Get L7 policies for a listener or all L7 policies.
get_load_balancer_l7_rules
Get L7 rules for a specific L7 policy.
get_load_balancer_list
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_listeners
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_members
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_pools
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_providers
Get load balancer providers.
Returns: JSON string containing providers information
get_load_balancer_quotas
Get load balancer quotas for a project or all projects.
get_network_details
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_project_details
Get OpenStack project details (similar to 'openstack project list/show').
get_quota
Get quota information for projects (similar to 'openstack quota show').
get_resource_monitoring
Monitors real-time resource usage across the OpenStack cluster.
Functions:
- Monitor cluster-wide CPU, memory, and storage usage rates
- Collect hypervisor statistics and resource allocation
- Track resource utilization trends and capacity planning data
- Provide resource usage summaries and utilization percentages
Use when user requests resource monitoring, capacity planning, usage analysis, or performance monitoring.
Returns: Resource monitoring data in JSON format with cluster summary, hypervisor details, and usage statistics.
get_role_assignments
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.
Returns: List of role assignments with detailed scope information in JSON format.
get_routers
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.
Returns: List of routers with detailed configuration in JSON format.
get_security_groups
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.
Returns: List of security groups with detailed rules in JSON format.
get_server_events
Get recent events for a specific server
get_server_groups
List all server groups with their details
Returns: JSON string with server groups information
get_server_volumes
Get all volumes attached to a specific server
get_service_status
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.
Returns: Service status information in JSON format with service details and health summary.
get_usage_statistics
Get usage statistics for projects (similar to 'openstack usage list' command).
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
- Calculate usage summary across all projects
Use when user requests usage statistics, billing information, resource consumption analysis, or project usage reports.
get_user_list
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.
Returns: List of users with detailed information in JSON format.
get_volume_list
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.
Returns: Detailed volume list in JSON format with volume information, attachments, and metadata.
get_volume_snapshots
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.
Returns: List of volume snapshots with detailed information in JSON format.
get_volume_types
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.
Returns: List of volume types with detailed specifications in JSON format.
search_instances
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
BEFORE YOU INSTALL
What to know first
Tools you get
41 tools when we connected; the project documents 93. Every default tool is a read; the set_* modify tools register only with ALLOW_MODIFY_OPERATIONS=true, and changing it requires a restart.
Requires
- uvx on PATH
- OS_AUTH_HOST in your environment
- OS_USERNAME in your environment
- OS_PASSWORD in your environment
- OS_PROJECT_NAME in your environment
Optional
REMOTE_SECRET_KEY in your environment
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-openstack-opsMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-openstack-ops": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mcp-openstack-ops"
],
"env": {
"OS_AUTH_HOST": "<YOUR_OS_AUTH_HOST>",
"OS_AUTH_PORT": "5000",
"OS_PROJECT_NAME": "<YOUR_OS_PROJECT_NAME>",
"OS_USERNAME": "<YOUR_OS_USERNAME>",
"OS_PASSWORD": "<YOUR_OS_PASSWORD>",
"OS_USER_DOMAIN_NAME": "Default",
"OS_PROJECT_DOMAIN_NAME": "Default",
"OS_REGION_NAME": "RegionOne",
"OS_IDENTITY_API_VERSION": "3",
"OS_INTERFACE": "internal",
"OS_COMPUTE_PORT": "8774",
"OS_NETWORK_PORT": "9696",
"OS_VOLUME_PORT": "8776",
"OS_IMAGE_PORT": "9292",
"OS_PLACEMENT_PORT": "8780",
"OS_HEAT_STACK_PORT": "8004",
"OS_HEAT_STACK_CFN_PORT": "18888",
"ALLOW_MODIFY_OPERATIONS": "false",
"MCP_LOG_LEVEL": "INFO"
}
}
}
}Claude Desktop — multiple projects
CLAUDE DESKTOP — MULTIPLE PROJECTS · JSON
{
"mcpServers": {
"openstack-production": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mcp-openstack-ops"
],
"env": {
"OS_PROJECT_NAME": "production",
"OS_USERNAME": "admin",
"OS_PASSWORD": "<YOUR_OS_PASSWORD>",
"OS_AUTH_HOST": "192.168.35.2"
}
},
"openstack-development": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mcp-openstack-ops"
],
"env": {
"OS_PROJECT_NAME": "development",
"OS_USERNAME": "admin",
"OS_PASSWORD": "<YOUR_OS_PASSWORD>",
"OS_AUTH_HOST": "192.168.35.2"
}
},
"openstack-testing": {
"command": "uvx",
"args": [
"--python",
"3.12",
"mcp-openstack-ops"
],
"env": {
"OS_PROJECT_NAME": "testing",
"OS_USERNAME": "admin",
"OS_PASSWORD": "<YOUR_OS_PASSWORD>",
"OS_AUTH_HOST": "192.168.35.2"
}
}
}
}One entry per OpenStack project, each with its own OS_PROJECT_NAME. The README's version of this block starts each entry with python -m mcp_openstack_ops, which only works where the package is installed into that python; these entries use the same uvx launch as the single-project setup instead. admin and 192.168.35.2 are samples; yours are your OpenStack username and host. Copy any other OS_* settings you need from the single-project block.
Any MCP client — HTTP
ANY MCP CLIENT — HTTP · JSON
{
"mcpServers": {
"mcp-openstack-ops": {
"type": "streamable-http",
"url": "http://<YOUR_SERVER>:8000/mcp",
"headers": {
"Authorization": "Bearer <YOUR_SECURE_SECRET_KEY>"
}
}
}
}For a server you run yourself in streamable-http mode. With REMOTE_AUTH_ENABLE=true and REMOTE_SECRET_KEY in that server's .env (or --auth-enable --secret-key), the value after Bearer is that same key, and <YOUR_SERVER> is the server's address. The Claude Desktop setups run over stdio and need neither.
Clients spell the "type" value differently: Claude Code and VS Code use "http", Cline uses "streamableHttp", and Roo Code uses "streamable-http". Claude Desktop does not accept a URL entry in its config file; remote servers go under Settings → Connectors.
