Add New MCP-Server - MCP-OpenStack-Ops (https://github.com/call518/MC…

[call518]

…P-OpenStack-Ops)

Description

This PR adds a new server entry to the modelcontextprotocol/servers repository: MCP-OpenStack-Ops, hosted at call518/MCP-OpenStack-Ops. The change updates README.md of the servers list, inserting this server along with its link and basic metadata.

Server Details

• Server: New server
• Changes to: README.md (adding entry to servers list), metadata (name, link, description)

Motivation and Context

MCP-OpenStack-Ops is an MCP (Model Context Protocol) server providing professional operations automation for OpenStack environments. Features include cluster monitoring, instance/volume/network management, safety controls, etc. By including it in the official servers listing, users of MCP will more easily find, evaluate, and leverage this server for OpenStack-based infrastructure automation.

How Has This Been Tested?

• Verified that the README link to call518/MCP-OpenStack-Ops is correct and leads to its GitHub repository. :contentReference[oaicite:0]{index=0}
• Checked that metadata (server name, short description) conforms to other entries in modelcontextprotocol/servers.
• Read through the call518/MCP-OpenStack-Ops README to ensure its features (transports, tools, safety controls, etc.) are described clearly. :contentReference[oaicite:1]{index=1}

Breaking Changes

• None.
• Existing MCP clients/configurations do not need change; this is purely a documentation/listing addition.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

• Repository: call518/MCP-OpenStack-Ops — GitHub link: https://github.com/call518/MCP-OpenStack-Ops :contentReference[oaicite:3]{index=3}
• License: MIT (as per repo header) :contentReference[oaicite:4]{index=4}
• Key features include: supports stdio and streamable-HTTP transports; OpenStack SDK integration; tools for cluster monitoring, instance/volume/network operations; includes safety controls / guardrails. :contentReference[oaicite:5]{index=5}