MCP-OpenStack-Ops provides comprehensive management and monitoring capabilities for OpenStack cloud infrastructure with a focus on safety and single-project scope. It enables AI assistants to interact with OpenStack resources while maintaining strict tenant isolation and configurable access controls. Key features: - Project-scoped operations that enforce resource ownership within a single tenant boundary - 90+ purpose-built tools covering compute (Nova), networking (Neutron), storage (Cinder), images (Glance), identity (Keystone), orchestration (Heat), and load balancing (Octavia) - Bulk operations with filtering capabilities across instances, volumes, networks, images, and snapshots - Safety-gated write operations that require explicit `ALLOW_MODIFY_OPERATIONS=true` configuration to prevent accidental changes - Real-time health monitoring, service status checks, and resource utilization insights - Unified instance queries with pagination and multiple search modes - Server audit trails, hypervisor details, and availability zone information - Connection caching and flexible deployment options including Docker and PyPI

MCP-OpenStack-Ops

> MCP OpenStack Operations Server: A comprehensive MCP (Model Context Protocol) server providing OpenStack project management and monitoring capabilities with built-in safety controls and single-project scope.

[](https://opensource.org/licenses/MIT)

[](https://smithery.ai/server/@call518/mcp-openstack-ops) [](https://www.buymeacoffee.com/call518)

[](https://github.com/call518/MCP-OpenStack-Ops/actions/workflows/pypi-publish.yml)

---

Architecture & Internal (DeepWiki)

[](https://deepwiki.com/call518/MCP-OpenStack-Ops)

---

Features

> ⚠️ Compatibility Notice: This MCP server is developed and optimized for OpenStack Epoxy (2025.1) as the primary target environment. However, it is compatible with most modern OpenStack releases (Dalmatian, Caracal, Bobcat, etc.) as the majority of APIs remain consistent across versions. Only a few specific API endpoints may require adaptation for full compatibility with older releases. > > 🚧 Coming Soon: Dynamic multi-version OpenStack API compatibility is actively under development and will be available in upcoming releases, providing seamless support for all major OpenStack deployments automatically.

🔧 OpenStackSDK Version Customization for Older Releases

Officially Supported Releases:

For older OpenStack releases (Wallaby, Caracal, Bobcat, etc.), you may need to customize the OpenStackSDK version to match your environment. The SDK version must be changed in BOTH files:

Step 1: Modify Dockerfile.MCP-Server

RUN pip install \
        'uv>=0.8.5' \
        'mcpo>=0.0.17' \
        'fastmcp>=2.12.3' \
        'aiohttp>=3.12.0' \
        'openstacksdk==3.1.1' \  # ← Change to your required version (e.g., 3.1.1 for Wallaby)
        'python-dotenv>=1.0.0'

Step 2: Modify pyproject.toml

dependencies = [
    "fastmcp>=2.12.3",
    "openstacksdk==3.1.1",  # ← Must match Dockerfile version
    "python-dotenv>=1.1.1",
    # ... other dependencies
]

Step 3: Rebuild Docker Image

docker-compose build --no-cache mcp-server
docker-compose up -d

OpenStackSDK Version Reference: | OpenStack Release | Recommended SDK Version | Notes | |-------------------|------------------------|-------| | Epoxy (2025.1) | >=3.3.0 | Current default | | Dalmatian (2024.2) | >=3.2.0 | Fully compatible |