Infomaniak MCP Agent vs Next Devtools MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Infomaniak MCP Agent vs Next Devtools MCP
In-depth architectural comparison of the Infomaniak MCP Agent and Next Devtools 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
Infomaniak MCP Agent
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Next Devtools MCP
Cloud Platforms · Local stdio
Quality: 86/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose Infomaniak MCP Agent if you need specialized Cloud Platforms tools running via a local process. Choose Next Devtools 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 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.
Infomaniak MCP Agent is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Next Devtools MCP belongs to Cloud Platforms using local stdio subprocess. Select Infomaniak MCP Agent when you need capabilities focused on cloud platforms and Next Devtools MCP when you require tools for cloud platforms.
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).
infomaniak_list_sites
Sites on a given web hosting (with applications).
+66 more tools listed on main page
Next Devtools MCP Tools (4)
nextjs_index
Discover running Next.js dev servers and list each one's runtime MCP tools.
nextjs_call
Call a runtime tool on a discovered server (errors, routes, logs, Server Actions).
nextjs_docs
Gateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
browser_eval
Gateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.
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.
Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.