infomaniak-mcp-server

A remote Model Context Protocol server that gives AI assistants (Claude, Cursor, VS Code…) access to the whole Infomaniak API, with a web admin portal to manage who can do what.

Unofficial project, not affiliated with or endorsed by Infomaniak. "Infomaniak" is a trademark of Infomaniak Network SA. Part of the catalog relies on undocumented API operations that may change or break without notice.

Features

• The whole API, a handful of tools. 1,787 operations — domains & DNS, web hosting, kDrive, Mail, kSuite, kChat, Public Cloud, Swiss Backup, streaming, VOD, newsletters… — reachable through six tools instead of one tool per endpoint. Every call is validated against the catalog.

• Several accounts. One server, many Infomaniak logins and organisations; the assistant picks the right one per call ("list the domains of ACME").

• Fine-grained access. MCP tokens with read-only mode, allowed API categories, IP allow-list and expiry; "Sign in with Infomaniak" (OAuth) with rules per user, e-mail or domain.

• Safe by default. Deletions, restores, orders and transfers need the user's explicit confirmation; ordering and billing categories are off until you enable them.

• Admin portal. Guided first-launch setup, then everything is managed from a web UI (English / French), applied without restart.

• Easy to run. One container image (amd64 / arm64), a SQLite file for state, stateless MCP endpoint.

Related MCP server: external-ai-ecosystem-gateway

Quick start

podman run -d --name infomaniak-mcp-server \
  -p 3000:3000 -p 127.0.0.1:9090:9090 \
  -v infomaniak-mcp-data:/data \
  ghcr.io/kallioli/infomaniak-mcp-server:latest

podman logs infomaniak-mcp-server | grep "Setup code"

Open http://localhost:9090, enter the setup code and follow the wizard:

1. Admin account — the one-time code from the logs proves you own the server.

2. Access & security — public URL, reverse proxy, global read-only mode.

3. Infomaniak connection — paste an API token created in the Infomaniak Manager (at least the accounts scope, plus the products you want to drive); it is tested live and you pick a default organisation.

4. OAuth (optional) — enables "Sign in with Infomaniak" for claude.ai.

5. MCP token — generated with a ready-to-paste client command.

Docker works the same way (docker run … with the same options).

Connecting a client

The MCP endpoint is http://<host>:3000/mcp (or your public HTTPS URL).

Claude Code, with an MCP token from the portal:

claude mcp add --transport http infomaniak https://mcp.example.com/mcp \
  --header "Authorization: Bearer imkt_…"

Claude Code with OAuth: claude mcp add --transport http infomaniak https://mcp.example.com/mcp, then /mcp to sign in.

claude.ai: Settings → Connectors → Add custom connector → https://mcp.example.com/mcp. claude.ai reaches the server from the internet, so it needs a public HTTPS URL and OAuth enabled.

Claude Desktop and other clients without custom headers can go through mcp-remote:

{
  "mcpServers": {
    "infomaniak": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "http://localhost:3000/mcp", "--header", "Authorization:${AUTH}"],
      "env": { "AUTH": "Bearer imkt_…" }
    }
  }
}

How it works

Tools

The assistant searches the catalog, reads the operation's description, then calls it. kChat calls are routed to <team>.kchat.infomaniak.com.

Connections and organisations

Two levels, chosen per call:

• Connection — a set of Infomaniak credentials: your company, customer A, customer B… An MCP token is granted one or more connections, one being its default, and never sees the others. A read-only connection refuses writes.

• Organisation — the Infomaniak accounts a login can manage. Each connection can have a default one.

infomaniak_get and infomaniak_request take account (organisation name or id) and, when several connections are available, connection. The token's own choices are listed in the tool schema, so the assistant needs no extra call to pick them; an ambiguous name is refused with the candidates. The organisation is filled into the endpoint's account_id / account parameter when the call does not set it.

Confirmation of risky operations

Every DELETE, restore, checkout and transfer — documented or not — needs the user's explicit confirmation. When the client supports MCP elicitation, the server asks the user directly; otherwise the call is refused until the assistant confirms with the user and retries with confirm: true. infomaniak_describe_operation shows needsConfirmation.

Undocumented operations

The official OpenAPI spec misses part of what the Infomaniak Manager does with API tokens. spec/infomaniak-extensions.openapi.json adds those operations (web hosting, /domain DNS API, orders and cart, invoicing, account users and permissions…), fixes some official ones and adds missing parameters. They are shown as undocumented: true, and verified: false when they were never executed with a token. The Orders and Invoicing & Payments categories are disabled by default. See docs/undocumented-operations.md.

Authentication

Modes can be combined:

OAuth

1. Create an OAuth application in the Infomaniak Manager with the redirect URI https://<your-server>/oauth/callback.

2. Enter the public URL, client id and client secret in the portal (wizard or Settings).

3. Add the server in your client with just its URL; the client handles the login.

By default, someone who signs in acts with their own Infomaniak login only. The OAuth access page grants more through rules matching the user by Infomaniak user id, e-mail address or e-mail domain: shared connections, the user's own login (shown as the Personal connection), read-only mode and allowed categories. E-mail and domain rules only match addresses Infomaniak reports as verified, and rules are re-evaluated on every request. The policy for users no rule matches is either personal login only or deny.

Under the hood, Infomaniak only accepts confidential OAuth clients while MCP clients register dynamically and use PKCE, so the server acts as the authorization server for MCP clients and as a confidential client of Infomaniak. It stores nothing: clients, codes and tokens are AES-256-GCM sealed. Access tokens expire with the Infomaniak token they wrap; changing the OAuth secret signs everyone out.

Admin portal

Runs on its own port (default 9090). Keep it private: publish only the MCP port through your reverse proxy and reach the portal through a VPN, an SSH tunnel or a restricted virtual host.

Configuration

Settings made in the portal are stored in the database and applied without restart. Environment variables take precedence and lock the matching field in the portal, which suits GitOps deployments. See .env.example for details.

Put the MCP endpoint behind HTTPS before exposing it: tokens travel in request headers.

Development

npm install
npm run dev                  # MCP server and admin API in watch mode
npm run dev:admin            # admin UI with hot reload on :5173 (API proxied to :9090)
npm test                     # vitest
npm run typecheck
npm run build                # server and admin UI into dist/
npm run catalog              # rebuild src/catalog.json from the live spec and the extensions
npm run extensions:sanitize  # strip real data from a new extensions file

Local stdio mode: INFOMANIAK_API_TOKEN=… node dist/index.js --stdio.

Build the image yourself with podman build --format docker -t infomaniak-mcp-server . (--format docker keeps the health check) or docker build -f Containerfile -t infomaniak-mcp-server .. The CI publishes latest from main and X.Y.Z / X.Y from version tags.

License

MIT