In-depth architectural comparison of the Python Openstackmcp Server and Hub MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Python Openstackmcp Server
Cloud Platforms · Local stdio
Quality: 57/100 (Good) | Auth: other
Hub MCP
Cloud Platforms · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Verdict Summary: Choose Python Openstackmcp Server if you need specialized Cloud Platforms tools running via a local process. Choose Hub MCP if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Python Openstackmcp Server when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: OS_CLIENT_CONFIG_FILE.
Python Openstackmcp Server is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Hub MCP belongs to Cloud Platforms using local stdio subprocess. Select Python Openstackmcp Server when you need capabilities focused on cloud platforms and Hub MCP when you require tools for cloud platforms.
Get the list of OpenStack images with optional filtering.
The filtering behavior is as follows:
- By default, all available images are returned without any filtering applied.
- Filters are only applied when specific values are provided by the user.
create_image
Create a new Openstack image.
This method handles both cases of image creation:
1. If a volume is provided, it creates an image from the volume.
2. If no volume is provided, it creates an image using the Image imports method
import_options field is required for this method.
Following import methods are supported:
- glance-direct: The image data is made available to the Image service via the Stage binary
- web-download: The image data is made available to the Image service by being posted to an accessible location with a URL that you know.
- must provide a URI to the image data.
- copy-image: The image data is made available to the Image service by copying existing image
- glance-download: The image data is made available to the Image service by fetching an image accessible from another glance service specified by a region name and an image id that you know.
- must provide a glance_region and glance_image_id.
+63 more tools listed on main page
Hub MCP Tools (35)
search
Search repositories and content using Search V4 API
query
Search query parameter (string, required)
architectures
Filter on architectures (string, optional)
badges
Filter by image content type badges (string, optional)
categories
Filter on categories (string, optional)
extension_reviewed
Filter on reviewed extensions (boolean, optional)
from
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)