SuperAPI AI Directory
Partner with us中文AI newsFavorites
All toolsAI agentsinfomaniak-mcp-agent

infomaniak-mcp-agent

Unofficial Infomaniak integration: web hosting, mail, kDrive, domains, DNS, FTP/SSH users and more, with two-phase commits and undo for destructive actions.

Open website

About this tool

Purpose

infomaniak-mcp-agent is an unofficial Model Context Protocol (MCP) server whose goal is to let users drive automated operations across an entire Infomaniak account through natural language (such as Claude and other MCP clients). Infomaniak is a Swiss independent cloud provider with a vast product line (Web hosting, email kDrive, kChat, DNS, AI cloud, Swiss Backup, etc.), but its API is divided into a publicly documented part and a manager-only private part, which means real workflow automation usually requires a browser session or custom scripts. This project fills that gap by exposing all functionality through a single MCP server.

Main capabilities

The server provides 78 tools spread across 22 domains, mainly including:

  • Introspection tools (starting point): infomaniak_overview, infomaniak_help (fuzzy search for tools by intent), infomaniak_explain (outputs the full JSON schema of a tool), infomaniak_history (lists all destructive operations in the current session), infomaniak_undo (undoes reversible operations).
  • Organization and products: organizations, product lists, etc.
  • Web hosting sites: list, create, delete sites; manage additional FQDNs (Apache vhost / DocumentRoot bound to an existing site, allowing multiple domains to be served with a single installation without creating a new site); SSL certificates.
  • Databases: database operations, database user management (note: the related tools accept a grants array declaring each database the user can access; omitting it sets no access permissions; before updating, you must first call infomaniak_get_database_user to copy the current permissions, otherwise access will be silently revoked; this is also the standard way to revoke authorization. For this purpose it uses manager-private endpoints, because the public API's PATCH will accept a password, change the password, and silently clear permissions and applications. Prefer these tools over executing MariaDB ALTER USER / SET PASSWORD directly via SSH, because the manager is the source of truth for managed database credentials).
  • FTP / SSH users: management.
  • Identity: query "who am I".
  • Account / organization (deep): deep account operations.
  • kDrive (deep, manager-private): list drives, browse files.
  • VPS / cloud servers: management.
  • Node.js applications (cloud server hosting_3): all Node.js tools are manager-private and require INFOMANIAK_AUTH_MODE=auto (Chrome cookies) or manual (SASESSION + MANAGER-XSRF-TOKEN environment variables).
  • Email (kSuite): mailboxes, aliases, signatures, backups, redirects, all supporting CRUD.
  • Domains and DNS: full record CRUD, DNSSEC enable/disable/check.
  • Swiss Backup: list slots.
  • AI tools: list products and public model catalog.
  • URL short links: full CRUD.
  • Account audit: soon-to-expire domains, locked products, operations in progress.
  • Workflow tools: provision_site_full, audit_dns_zones.
  • Generic API escape hatch: call any documented endpoint.

Usage

  1. Installation: it is recommended to fetch the latest version on demand via npx (no installation step required; the latest version is resolved and cached on first call); you can also install globally or from the repository to pin to a specific commit.
  2. Configure Claude Desktop: add the configuration in ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %AppData%\Claude\claude_desktop_config.json on Windows, and restart Claude Desktop for it to take effect. Claude Code can also be configured.
  3. Authentication: two types of credentials are required.
    • Bearer token (required): log in to your Infomaniak account and visit manager.infomaniak.com/v3/ng/profile/user/token/list, click "Create a token", set a long validity period, copy the value and set it to INFOMANIAK_API_TOKEN.
    • Manager session (automatic, recommended): The Manager private API does not accept Bearer tokens or OAuth (Infomaniak only exposes the openid profile email phone scopes to third-party apps; web, mail, etc. are reserved). Therefore, under INFOMANIAK_AUTH_MODE=auto (default), MCP uses chrome-cookies-secure to read on demand the SASESSION and MANAGER-XSRF-TOKEN cookies from an already logged-in manager.infomaniak.com in local Chrome. Nothing is written to disk; cookies are kept in memory only during a single operation. When the session expires, simply reload manager.infomaniak.com in Chrome, and MCP will fetch new cookies on the next call.
    • Manager session (manual fallback): For headless environments or troubleshooting. Open Chrome DevTools, Application → Cookies, copy SASESSION and MANAGER-XSRF-TOKEN (URL-encoded, paste as-is, MCP will decode), and set them as environment variables.
  4. Typical conversation examples: You can ask to list domains expiring within 60 days, create a site on a specified hosting, add a TXT record, query database disk usage, create a mailbox and forward, check kDrive capacity, audit the entire account, revoke the last DNS change in this session, etc. All destructive operations return a plan plus a single confirmation token; nothing is changed until the token is called back.

How the "agent" design differs from an ordinary wrapper

  • Guided conversation: When creating a site, it asks step by step (which organization, which hosting, root domain or subdomain, what type, confirm summary), rather than requiring the user to know in advance which tool to call.
  • Two-phase commit: Every destructive operation returns a plan with a single-use confirmation token (60-second TTL); nothing is changed until the token is called back.
  • Preflight checks: Checks for conflicts (an existing FQDN) before calling the API, busy hosting, expired domains).
  • Actionable errors: each error explains what happened, why, and what to do next.
  • Introspection: infomaniak_overview, infomaniak_help, infomaniak_explain provide on-demand context, with no need to memorize the tool catalog.
  • Session memory: infomaniak_history lists every destructive operation in the current session, and infomaniak_undo reverts reversible operations.

Use cases

Suitable for users who need to automate the daily operations of an Infomaniak account via natural language, such as bulk-managing DNS records, creating sites or mailboxes, auditing soon-to-expire domains and SSL, managing database user permissions, browsing kDrive, etc. Works with any MCP-capable client: Claude Desktop, Claude Code, Cursor, Cline, Continue, Zed AI, and MCP Inspector for debugging.

Limitations and caveats

  • Unofficial status: This project is not affiliated with, endorsed by, or sponsored by Infomaniak Network SA; it is community-driven and MIT-licensed.
  • Reverse-engineered endpoints: Write operations rely on reverse-engineered manager endpoints (manager.infomaniak.com/proxy/...). Infomaniak may change these endpoints without notice, and long-term compatibility cannot be guaranteed.
  • How it was built: The project was rapidly built via LLM-driven terminal sessions ("vibe-coding") and tested live on real accounts. It runs well in the maintainer's local environment with a fully green pipeline (TypeScript strict, ESLint, Prettier, 78 tests, build, CodeQL, gitleaks), but depending on account topology, plan tier, scopes, or changes by Infomaniak itself, you may encounter (potentially major) defects. When filing an issue, include the exact tool call, input, response (with tokens/cookies/customer names redacted), and environment (Node version, OS, MCP client).
  • Rate limits: api.infomaniak.com enforces a hard limit of 60 requests/minute. The MCP automatically rate-limits using a token bucket and briefly queues during bursts.
  • Site creation directory restriction: When creating a site, directories other than /sites/ are not supported; otherwise the manager backend silently does nothing.
  • Manager session cookie expiration: Usually expires every few hours or when Chrome is closed; reopen manager.infomaniak.com to refresh.
  • Concurrency limit: Only one concurrent operation is allowed per hosting at a time. Infomaniak returns 400 operation_in_progress for concurrent POSTs to the same hosting, and the MCP serializes write calls per hosting.
  • WordPress installation: Intentionally out of scope. You can use this MCP to create an empty site, then install WP from the manager wizard (the applications/add flow uses an undocumented step-by-step wizard and is too fragile to automate).
  • No hosted/SaaS version: This server runs on the user's own machine with their own credentials; there is no hosted SaaS, no proxy, and no telemetry.
  • Future roadmap (not yet implemented): kDrive writes (upload, download, move, share, archive), Newsletter (campaigns, contacts), kChat (no public API; reverse engineering required), the provision_wordpress_site workflow, Swiss Backup writes, increasing per-tool happy-path test coverage to 70%, and MCPB packaging for one-click installation in Claude Desktop.
  • AI tool scope: Only infomaniak_list_ai_products and infomaniak_list_ai_models are exposed for discovering products and public models; their inference endpoints are intentionally not wrapped (for inference, use the OpenAI-compatible API directly).

Related tools

Browse category