In-depth architectural comparison of the Hub MCP and Infomaniak MCP Agent 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
Hub MCP
Cloud Platforms · Local stdio
Quality: 80/100 (Excellent) | Auth: API Key required
Infomaniak MCP Agent
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Verdict Summary: Choose Hub MCP if you need specialized Cloud Platforms tools running via a local process. Choose Infomaniak MCP Agent 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 Hub MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Official MCP server to interact with Docker Hub, providing access to repositories, hub search and Docker Hardened Images
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.
Tools & Capabilities Breakdown
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)
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).
Hub MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infomaniak MCP Agent belongs to Cloud Platforms using local stdio subprocess. Select Hub MCP when you need capabilities focused on cloud platforms and Infomaniak MCP Agent when you require tools for cloud platforms.
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)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
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).
infomaniak_list_organizations
Accounts you have technical access to.
infomaniak_list_hostings
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).