mcp-openstack-ops 1.0.0

OpenStack operations automation MCP server

MCP-OpenStack-Ops

MCP OpenStack Operations Server: A comprehensive MCP (Model Context Protocol) server providing OpenStack cluster management and monitoring capabilities. This server enables AI assistants to interact with OpenStack infrastructure through standardized tools for real-time monitoring, resource management, and operational tasks.

---

Features

• ✅ OpenStack Integration: Direct integration with OpenStack SDK for real-time cluster operations. (SDK Release Matrix)
• ✅ Large-Scale Environment Support: Pagination and limits for environments with thousands of instances.
• ✅ Comprehensive Monitoring: Enhanced cluster status reports with hypervisor health, resource utilization (CPU/memory/disk), service monitoring, health scoring, and issue detection.
• ✅ Complete Service Coverage: 24 comprehensive tools covering Identity, Compute, Network, Storage, Image, and Orchestration services.
• ✅ Advanced Instance Management: Start, stop, restart, pause/unpause OpenStack instances with pagination support.
• ✅ Enterprise Features: User management, role assignments, keypair management, floating IP operations, volume snapshots, Heat orchestration.
• ✅ Intelligent Search: Flexible instance search with partial matching and case-sensitive options.
• ✅ Volume Operations: Create, delete, list, and manage OpenStack volumes.
• ✅ Network Analysis: Detailed network, subnet, router, and security group information.
• ✅ Connection Optimization: Global connection caching and automatic retry mechanisms.
• ✅ Flexible Transport: Support for both stdio and streamable-http transports.
• ✅ Comprehensive Logging: Configurable logging levels with structured output and performance tracking.
• ✅ Environment Configuration: Support for environment variables and CLI arguments.
• ✅ Error Handling: Robust error handling and configuration validation with fallback data.
• ✅ Docker Support: Containerized deployment with Docker Compose.

---

MCP Tools Available

🔍 Monitoring & Status Tools

1. get_cluster_status - Enhanced comprehensive cluster analysis
   • Compute nodes: hypervisor status, resource utilization (CPU/memory/disk)
   • Instance analysis: status distribution, availability zones, detailed info
   • Network resources: external networks, floating IPs, routers, security groups
   • Storage resources: volumes by status, snapshots, volume types
   • Service status: service health, compute services monitoring
   • Health scoring: overall cluster health with issue detection
2. get_service_status - OpenStack service health and API endpoint status
3. get_instance_details - Detailed information for specific instances with pagination support
   • Supports filtering by instance names or IDs
   • Pagination parameters: limit (default 50, max 200), offset (default 0)
   • Performance metrics and processing time tracking
4. search_instances - Advanced instance search with flexible criteria
   • Search fields: name, status, host, flavor, image, availability_zone, all
   • Partial string matching with case-sensitive options
   • Optimized 2-phase search for large environments
5. get_instance_by_name - Quick lookup for specific instance by name
6. get_instances_by_status - Filter instances by operational status
7. monitor_resources - Real-time resource usage and capacity monitoring

🌐 Network Management Tools

8. get_network_details - Network, subnet, router, and security group details
9. get_floating_ips - Floating IP allocation and status information
10. manage_floating_ip - Create, delete, associate/disassociate floating IPs
11. get_routers - Router status and configuration details
12. get_security_groups - Security group rules and configuration

💾 Storage Management Tools

13. manage_volume - Volume management operations (create/delete/list/extend)
14. get_volume_types - Available volume types and specifications
15. get_volume_snapshots - Volume snapshot status and management
16. manage_snapshot - Create, delete, and manage volume snapshots

⚙️ Instance & Compute Management

17. manage_instance - Instance lifecycle operations (start/stop/restart/pause/unpause)
18. get_keypair_list - SSH keypair management and listing
19. manage_keypair - Create, delete SSH keypairs for instance access

👥 Identity & Access Management

20. get_user_list - OpenStack user accounts and details
21. get_role_assignments - User role assignments and permissions

🖼️ Image Management

22. manage_image - Create, delete, and manage OpenStack images

🔥 Orchestration (Heat) Tools

23. get_stacks - Heat stack status and information
24. manage_stack - Create, delete, and manage Heat orchestration stacks

---

Quick Start

1. Environment Setup

# Clone and navigate to project
cd MCP-OpenStack-Ops

# Install dependencies
uv sync

# Configure environment
cp .env.example .env
# Edit .env with your OpenStack credentials

2. OpenStack Configuration

Configure your .env file with OpenStack credentials:

# OpenStack Authentication
OS_AUTH_URL=https://your-openstack:5000/v3
OS_IDENTITY_API_VERSION=3
OS_USERNAME=your-username
OS_PASSWORD=your-password
OS_PROJECT_NAME=your-project
OS_PROJECT_DOMAIN_NAME=default
OS_USER_DOMAIN_NAME=default
OS_REGION_NAME=RegionOne

# MCP Server Configuration (optional)
MCP_LOG_LEVEL=INFO
FASTMCP_TYPE=stdio
FASTMCP_HOST=127.0.0.1
FASTMCP_PORT=8080

3. Run Server

For Development & Testing

# Local testing with MCP Inspector
./scripts/run-mcp-inspector-local.sh

# Direct execution for debugging
uv run python -m mcp_openstack_ops --log-level DEBUG

For Production (Docker)

# Build and run with Docker Compose
docker-compose up -d

# Check logs
docker-compose logs -f mcp-server

For Claude Desktop Integration

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "openstack-ops": {
      "command": "uv",
      "args": ["run", "python", "-m", "mcp_openstack_ops"],
      "cwd": "/path/to/MCP-OpenStack-Ops"
    }
  }
}

---

Server Configuration

Command Line Options

uv run python -m mcp_openstack_ops --help

Options:
  --log-level {DEBUG,INFO,WARNING,ERROR,CRITICAL}
                        Logging level
  --type {stdio,streamable-http}
                        Transport type (default: stdio)
  --host HOST          Host address for HTTP transport (default: 127.0.0.1)
  --port PORT          Port number for HTTP transport (default: 8080)
  --auth-enable        Enable Bearer token authentication for streamable-http mode
  --secret-key SECRET  Secret key for Bearer token authentication

Environment Variables

Variable	Description	Default	Usage
OpenStack Authentication
OS_AUTH_URL	OpenStack Identity service URL	Required	Authentication endpoint
OS_USERNAME	OpenStack username	Required	User credentials
OS_PASSWORD	OpenStack password	Required	User credentials
OS_PROJECT_NAME	OpenStack project name	Required	Project scope
OS_IDENTITY_API_VERSION	Identity API version	3	API version
OS_PROJECT_DOMAIN_NAME	Project domain name	default	Domain scope
OS_USER_DOMAIN_NAME	User domain name	default	Domain scope
OS_REGION_NAME	OpenStack region	RegionOne	Regional scope
MCP Server Configuration
MCP_LOG_LEVEL	Logging level	INFO	Development debugging
FASTMCP_TYPE	Transport type	stdio	Rarely needed to change
FASTMCP_HOST	HTTP host address	127.0.0.1	For HTTP mode only
FASTMCP_PORT	HTTP port number	8080	For HTTP mode only
Authentication (Optional)
REMOTE_AUTH_ENABLE	Enable Bearer token authentication for streamable-http mode	false	Production security
REMOTE_SECRET_KEY	Secret key for Bearer token authentication	Required when auth enabled	Production security

Note: MCP servers typically use stdio transport. HTTP mode is mainly for testing and development.

---

Example Queries

For comprehensive tool usage examples and query patterns, see: Example Queries in Prompt Template

---

Performance Optimization

Large-Scale Environment Support

The MCP server is optimized for large OpenStack environments with thousands of instances:

Pagination Features:

• Default limits prevent memory overflow (50 instances per request)
• Configurable safety limits (maximum 200 instances per request)
• Offset-based pagination for browsing large datasets
• Performance metrics tracking (processing time, instances per second)

Search Optimization:

• 2-phase search process (basic info filtering → detailed info retrieval)
• Intelligent caching with connection reuse
• Selective API calls to minimize overhead
• Case-sensitive search options for precise filtering

Connection Management:

• Global connection caching with validity testing
• Automatic retry mechanisms for transient failures
• Connection pooling for high-throughput scenarios

Usage Examples:

# Safe large environment browsing
get_instance_details(limit=50, offset=0)     # First 50 instances
get_instance_details(limit=50, offset=50)    # Next 50 instances

# Emergency override for small environments
get_instance_details(include_all=True)       # All instances (use with caution)

# Optimized search for large datasets
search_instances("web", "name", limit=20)    # Search with reasonable limit

---

Development

Adding New Tools

Edit src/mcp_openstack_ops/mcp_main.py to add new MCP tools:

@mcp.tool()
async def my_openstack_tool(param: str) -> str:
    """
    Brief description of the tool's purpose.
    
    Functions:
    - List specific functions this tool performs
    - Describe the operations it enables
    - Mention when to use this tool
    
    Use when user requests [specific scenarios].
    
    Args:
        param: Description of the parameter
        
    Returns:
        Description of return value format.
    """
    try:
        logger.info(f"Tool called with param: {param}")
        # Implementation using functions.py helpers
        result = my_helper_function(param)
        
        response = {
            "timestamp": datetime.now().isoformat(),
            "result": result
        }
        
        return json.dumps(response, indent=2, ensure_ascii=False)
        
    except Exception as e:
        error_msg = f"Error: Failed to execute tool - {str(e)}"
        logger.error(error_msg)
        return error_msg

Helper Functions

Add utility functions to src/mcp_openstack_ops/functions.py:

def my_helper_function(param: str) -> dict:
    """Helper function for OpenStack operations"""
    try:
        conn = get_openstack_connection()
        
        # OpenStack SDK operations
        result = conn.some_service.some_operation(param)
        
        logger.info(f"Operation completed successfully")
        return {"success": True, "data": result}
        
    except Exception as e:
        logger.error(f"Helper function error: {e}")
        raise

---

Testing & Validation

Local Testing

# Test with MCP Inspector (recommended)
./scripts/run-mcp-inspector-local.sh

# Test with debug logging
MCP_LOG_LEVEL=DEBUG uv run python -m mcp_openstack_ops

# Validate OpenStack connection
uv run python -c "from src.mcp_openstack_ops.functions import get_openstack_connection; print(get_openstack_connection())"

Docker Testing

# Build and test in container
docker-compose build
docker-compose up -d

# Check container logs
docker-compose logs -f mcp-server

# Test HTTP endpoint (if using HTTP transport)
curl -X POST http://localhost:18005/mcp \
  -H "Content-Type: application/json" \
  -d '{"method": "tools/list"}'

---

🔐 Security & Authentication

Bearer Token Authentication

For streamable-http mode, this MCP server supports Bearer token authentication to secure remote access. This is especially important when running the server in production environments.

Configuration

Enable Authentication:

# In .env file
REMOTE_AUTH_ENABLE=true
REMOTE_SECRET_KEY=your-secure-secret-key-here

Or via CLI:

uv run python -m mcp_openstack_ops --type streamable-http --auth-enable --secret-key your-secure-secret-key-here

Security Levels

1. stdio mode (Default): Local-only access, no authentication needed
2. streamable-http + REMOTE_AUTH_ENABLE=false/undefined: Remote access without authentication ⚠️ NOT RECOMMENDED for production
3. streamable-http + REMOTE_AUTH_ENABLE=true: Remote access with Bearer token authentication ✅ RECOMMENDED for production

🔒 Default Policy: REMOTE_AUTH_ENABLE defaults to false if undefined, empty, or null. This ensures the server starts even without explicit authentication configuration.

Client Configuration

When authentication is enabled, MCP clients must include the Bearer token in the Authorization header:

{
  "mcpServers": {
    "openstack-ops": {
      "type": "streamable-http",
      "url": "http://your-server:8080/mcp",
      "headers": {
        "Authorization": "Bearer your-secure-secret-key-here"
      }
    }
  }
}

Security Best Practices

• Always enable authentication when using streamable-http mode in production
• Use strong, randomly generated secret keys (32+ characters recommended)
• Use HTTPS when possible (configure reverse proxy with SSL/TLS)
• Restrict network access using firewalls or network policies
• Rotate secret keys regularly for enhanced security
• Monitor access logs for unauthorized access attempts

Error Handling

When authentication fails, the server returns:

• 401 Unauthorized for missing or invalid tokens
• Detailed error messages in JSON format for debugging

---

Deployment

Local Development

# Test with MCP Inspector (recommended)
./scripts/run-mcp-inspector-local.sh

# Test with debug logging
MCP_LOG_LEVEL=DEBUG uv run python -m mcp_openstack_ops

# Validate OpenStack connection
uv run python -c "from src.mcp_openstack_ops.functions import get_openstack_connection; print(get_openstack_connection())"

Docker Testing

# Build and test in container
docker-compose build
docker-compose up -d

# Check container logs
docker-compose logs -f mcp-server

# Test HTTP endpoint (if using HTTP transport)
curl -X POST http://localhost:18005/mcp \
  -H "Content-Type: application/json" \
  -d '{"method": "tools/list"}'

Claude Desktop Integration

Add to your Claude Desktop configuration (claude_desktop_config.json):

Method 1: Local MCP (transport="stdio")

{
  "mcpServers": {
    "openstack-ops": {
      "command": "uv",
      "args": ["run", "python", "-m", "mcp_openstack_ops"],
      "cwd": "/path/to/MCP-OpenStack-Ops",
      "env": {
        "OS_AUTH_URL": "https://your-openstack:5000/v3",
        "OS_USERNAME": "your-username",
        "OS_PASSWORD": "your-password",
        "OS_PROJECT_NAME": "your-project",
        "MCP_LOG_LEVEL": "INFO"
      }
    }
  }
}

Method 2: Remote MCP (transport="streamable-http")

Without Authentication:

{
  "mcpServers": {
    "openstack-ops": {
      "type": "streamable-http",
      "url": "http://localhost:18005/mcp"
    }
  }
}

With Bearer Token Authentication (Recommended for production):

{
  "mcpServers": {
    "openstack-ops": {
      "type": "streamable-http", 
      "url": "http://localhost:18005/mcp",
      "headers": {
        "Authorization": "Bearer your-secure-secret-key-here"
      }
    }
  }
}

Production Deployment

# Using Docker Compose (recommended)
docker-compose up -d

# Manual Docker run
docker build -f Dockerfile.MCP-Server -t mcp-openstack-ops .
docker run -d --name mcp-openstack-ops \
  --env-file .env \
  -p 18005:8000 \
  mcp-openstack-ops

---

Troubleshooting

Common Issues

1. Authentication Errors

   • Verify OpenStack credentials in .env
   • Check network connectivity to OpenStack API endpoints
   • Validate user permissions and project access

2. Tool Execution Failures

   • Review logs with MCP_LOG_LEVEL=DEBUG
   • Ensure OpenStack services are accessible
   • Verify instance/volume/network names exist

3. Transport Issues

   • Use stdio for Claude Desktop integration
   • Use streamable-http for testing and development
   • Check port availability for HTTP transport

4. Authentication Issues (streamable-http mode)

   • Verify REMOTE_SECRET_KEY matches between server and client
   • Ensure Bearer token is included in client Authorization header
   • Check server logs for authentication error details
   • Confirm REMOTE_AUTH_ENABLE=true is set when using authentication

Getting Help

• Check logs for detailed error messages
• Validate OpenStack connectivity independently
• Test individual tools with MCP Inspector
• Review OpenStack SDK documentation for API requirements

---

License

This project is licensed under the MIT License - see the LICENSE file for details.

Contributing

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

HTTP Mode (Advanced)

For special testing scenarios only:

# Run HTTP server for testing
python -m src.mcp_openstack_ops.mcp_main \
  --type streamable-http \
  --host 127.0.0.1 \
  --port 8080 \
  --log-level DEBUG

Testing & Development

# Test with MCP Inspector
./scripts/run-mcp-inspector-local.sh

# Direct execution for debugging
python -m src.mcp_openstack_ops.mcp_main --log-level DEBUG

# Run tests (if you add any)
uv run pytest

---

Logging

The server provides structured logging with configurable levels:

2024-08-19 10:30:15 - mcp_main - INFO - Starting MCP server with stdio transport
2024-08-19 10:30:15 - mcp_main - INFO - Log level set via CLI to INFO
2024-08-19 10:30:16 - functions - DEBUG - Fetching data from source: example.com

---

Notes

• The script replaces mcp_openstack_ops (underscore), mcp-openstack-ops (hyphen), and mcp-openstack-ops (display name)
• Configuration validation ensures proper setup before server start
• If you need to rename again, revert changes or re-clone and re-run
• A backup pyproject.toml.bak is created when overwriting pyproject