Infomaniak MCP Agent vs Python Openstackmcp S… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Infomaniak MCP Agent vs Python Openstackmcp Server
In-depth architectural comparison of the Infomaniak MCP Agent and Python Openstackmcp Server 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
Infomaniak MCP Agent
Cloud Platforms · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Python Openstackmcp Server
Cloud Platforms · Local stdio
Quality: 57/100 (Good) | Auth: other
Verdict Summary: Choose Infomaniak MCP Agent if you need specialized Cloud Platforms tools running via a local process. Choose Python Openstackmcp Server 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 Infomaniak MCP Agent when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: INFOMANIAK_BEARER_TOKEN, INFOMANIAK_MANAGER_COOKIE.
Unofficial agentic MCP server for Infomaniak (Swiss cloud provider). 54 tools covering web hosting, mail, kDrive, domains, DNS, DNSSEC, FTP/SSH users, AI catalogue and more. Two-phase commit on every destructive operation, history & undo, transparent reverse-engineering of undocumented manager-private endpoints.
OpenStack MCP server for cloud infrastructure management based on openstacksdk.
Category & Scope
Tools & Capabilities Breakdown
Infomaniak MCP Agent Tools (78)
infomaniak_overview
Summary of organizations + products. Best first call.
infomaniak_help
Suggest tools matching a free-form intent ("create site", "list mailboxes"…).
infomaniak_explain
Returns the full definition (description + schemas) of a specific tool.
infomaniak_audit_account
Scan an organization for expirations / locked products / ongoing ops.
infomaniak_history
List destructive actions taken in this session.
infomaniak_undo
Reverse a session action when reversible (two-phase commit).
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Infomaniak MCP Agent is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Python Openstackmcp Server belongs to Cloud Platforms using local stdio subprocess. Select Infomaniak MCP Agent when you need capabilities focused on cloud platforms and Python Openstackmcp Server when you require tools for cloud platforms.
Web hostings (classic + Node.js) for one organization.
infomaniak_list_domains
Domains for one organization, with creation + expiration dates.
infomaniak_get_domain
Detail of one domain (DNS managed?, DNSSEC, errors).
infomaniak_find_site
Domain-first lookup.** Resolves a public domain (e.g. `example.com`) to `{account_id, hosting_id, hosting_label, site_id, full site object}`. Use this BEFORE any tool that needs `hosting_id + site_id`. Replaces iterating every hosting's `list_sites` (46+ API calls on a real fleet).
infomaniak_list_sites
Sites on a given web hosting (with applications).
+66 more tools listed on main page
Python Openstackmcp Server Tools (75)
get_servers
Get the list of Compute servers.
:return: A list of Server objects.
get_server
Get a specific Compute server.
create_server
Create a new Compute server.
get_flavors
Get flavors (server hardware configurations).
:return: A list of Flavor objects.
action_server
Perform an action on a Compute server.
update_server
Update a Compute server's name, hostname, or description.
delete_server
Delete a Compute server.
attach_volume
Attach a volume to a Compute server.
detach_volume
Detach a volume from a Compute server.
get_image
Get an OpenStack image by ID.
get_images
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.