MCP.Market

Infomaniak Agent MCP server

by Mogacode-ma·io.github.Mogacode-ma/infomaniak-mcp-agent·v0.15.1·8 stars

Unofficial Infomaniak MCP — hosting, Node.js, mail, DNS, kDrive, SSL, VPS, domains. 81 tools.

C66/100grade C
What users say
No reviews yet
Be the first
Safety scan
C66/100

full report

Adoption
Growing

8 stars

Reviews

Write one

Nobody has reviewed Infomaniak Agent yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Infomaniak Agent tools (78, 18 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • infomaniak_add_site_aliases

    Bind one or more additional FQDNs (including wildcards like `*.example.com`) to a web hosting site. Lets the site's Apache vhost / DocumentRoot serve those new domains too \u2014 no new site provisioning required. Two-phase commit. Asynchronous: returns a `progress_id`; the alias appears in `infomaniak_list_site_aliases` after a few seconds of provisioning. Manager-private.

  • infomaniak_api_call

    Escape hatch: call ANY Infomaniak public API endpoint (api.infomaniak.com) when no dedicated tool exists. GET runs immediately. POST/PUT/PATCH/DELETE follow the two-phase commit pattern. Manager-private (/proxy/...) endpoints are NOT reachable through this tool \u2014 use a typed tool instead.

  • infomaniak_audit_account

    Scan an Infomaniak organization for actionable issues: products expiring soon, products in maintenance, locked products, ongoing operations.

  • infomaniak_audit_dns_zones

    Bulk-read every domain owned by an account: number of DNS records and DNSSEC status per zone. Useful for spot-checking large fleets.

  • infomaniak_change_database_user_password

    Rotate a MariaDB user's password AND set its database grants atomically. Manager-private PATCH that preserves grants (the public-API PATCH silently wipes permissions; this uses the manager-private endpoint with the correct full-permissions-object shape). Two-phase commit. The `grants` array declares EVERY database this user should access \u2014 anything omitted is set to no-access. Tip: call `info

  • infomaniak_change_database_user_permissionswrite action

    Update which databases a MariaDB user can access (read/write/admin per DB). Does NOT change the password. Same manager-private endpoint as the password rotation. Two-phase commit. Anything not in `grants` is set to no-access \u2014 this is the canonical way to revoke a grant. Manager-private.

  • infomaniak_change_hosting_user_connection_type

    Promote or demote an FTP/SSH user: `ftp` = SFTP-only, `ssh` = full shell + SFTP. Two-phase commit. Does NOT change the password. Manager-private endpoint.

  • infomaniak_change_hosting_user_password

    Rotate the password of an FTP/SSH user on a web hosting. Two-phase commit. The `connection_type` field is required by Infomaniak (the manager UI always re-sends it); pass the user's current value to avoid changing it. Manager-private endpoint.

  • infomaniak_create_databasewrite action

    Create a new MariaDB database on a web hosting. Two-phase commit. Goes through the manager-private API because the public one silently no-ops on database POSTs.

  • infomaniak_create_hosting_userwrite action

    Create a new FTP / SSH user on a web hosting. Two-phase commit. Connection types: `ftp` (SFTP-only, no shell) or `ssh` (full shell + FTP). The password follows Infomaniak's default policy.

  • infomaniak_create_mailboxwrite action

    Create a new mailbox on a mail hosting. Two-phase commit: plan + token first, then apply with token. The password never appears in the plan output.

  • infomaniak_create_mailbox_aliaswrite action

    Add a new alias to an existing mailbox. Two-phase commit. The alias will receive emails delivered to the underlying mailbox.

  • infomaniak_create_redirectionwrite action

    Create a server-side mail redirection. Two-phase commit. Emails received at name@<domain> will be forwarded to every address in targets.

  • infomaniak_create_short_urlwrite action

    Create a new short URL pointing to a long target. Two-phase commit. Use infomaniak_short_urls_quota first if you're not sure you have headroom.

  • infomaniak_create_sitewrite action

    Creates a new site on an Infomaniak web hosting. Two-phase commit: first call returns a plan with a confirmation_token, second call (same params + token) actually creates the site.

  • infomaniak_delete_certificatewrite action

    Delete the SSL certificate of a site (the site will fall back to no HTTPS or Infomaniak's default cert until a new one is requested). Two-phase commit. The plan pulls the current certificate status so the caller can see what is about to be removed.

  • infomaniak_delete_databasewrite action

    Delete a MariaDB database. Two-phase commit, manager-private API. WARNING: the database content (tables, rows) is wiped and cannot be recovered without an Infomaniak backup.

  • infomaniak_delete_hosting_userwrite action

    Revoke a hosting user (FTP / SSH access). Two-phase commit. Existing files are not deleted.

  • infomaniak_delete_mailboxwrite action

    Delete a mailbox. Two-phase commit. WARNING: this also deletes all stored emails for that mailbox.

  • infomaniak_delete_redirectionwrite action

    Delete a mail redirection. Two-phase commit.

  • infomaniak_delete_sitewrite action

    Delete a site from an Infomaniak web hosting. Two-phase commit: first call returns a plan with the site preview + token, second call (same params + token) actually deletes. WARNING: this also wipes the site directory on the FTP backend after a short grace period.

  • infomaniak_delete_site_aliaswrite action

    Remove one alias FQDN from a web hosting site (the main FQDN cannot be removed). Two-phase commit. After this, the site's Apache vhost will no longer respond to the alias. Manager-private.

  • infomaniak_dns_create_recordwrite action

    Create a DNS record on an Infomaniak-managed zone. Two-phase commit: first call returns a plan + token, second call (same params + token) actually creates the record.

  • infomaniak_dns_delete_recordwrite action

    Delete a DNS record from an Infomaniak-managed zone. Two-phase commit: first call returns a plan with a preview of the record to delete + token, second call (same params + token) actually deletes.

  • infomaniak_dns_list_records

    List every DNS record on a zone managed by Infomaniak. Use the root domain (e.g. 'example.com'), not a subdomain.

  • infomaniak_dns_update_recordwrite action

    Update one or more fields of a DNS record. Two-phase commit: first call shows current vs proposed values + token; second call (same params + token) applies the update.

  • infomaniak_explain

    Returns the full definition of a specific tool \u2014 description, annotations, input parameters and output shape.

  • infomaniak_find_site

    Locate a domain (e.g. broz.be) in the Infomaniak account tree. Returns {account_id, hosting_id, site_id, hosting_label, full site object}. Use this BEFORE any tool that requires hosting_id + site_id (get_certificate, request_certificate, list_databases, etc.) when you only know the domain name. Significantly cheaper than calling list_hostings + list_sites manually because it short-circuits on the

  • infomaniak_get_account_full

    Full organization detail: legal entity, billing address(es), VAT, locale, timezone, logo URLs, support tier (premium=2), 2FA-required policy, your role (owner/admin/billing/user), user/owner counts, tags. Manager-private.

  • infomaniak_get_certificate

    Return the full SSL certificate detail for one site on a web hosting: provisioning state (`installed`, `updating`, `error`, \u2026), type (free/paid/custom) and sub-type (`lets_encrypt`, \u2026), issuer + organization, validity flags (`is_valid`, `is_expired`, `is_selfsigned`), issue and expiry timestamps, SHA-256 fingerprint, main FQDN in IDN form, ACME identifier errors and the timestamp of the

  • infomaniak_get_database

    Get the full detail of a specific database (disk usage, application, permissions, backups).

  • infomaniak_get_database_user

    Fetch the detail of a single MariaDB-level user (applications, permissions, link to phpMyAdmin).

  • infomaniak_get_domain

    Get detailed information about a domain (DNS management status, DNSSEC, IDN, errors).

  • infomaniak_get_domain_full

    Full domain detail including auth_code (EPP transfer code), transfer_status, trade_status, termination state, glue records, TLD/registry info, attached service (web hosting), DNS detail, DNS health diagnostic, owner (registrant), associated products on the domain AND its subdomains, and the DNS logs API URL. Accepts either domain_id or FQDN. Manager-private.

  • infomaniak_get_drive_full

    Full kDrive detail: name, total size (bytes), used size, creation/update timestamps, maintenance flag. Useful for storage usage monitoring. Manager-private \u2014 distinct from the existing `infomaniak_list_drives` which hits the public Bearer API.

  • infomaniak_get_mail_hosting_full

    Full mail hosting detail with diagnostic_dns (MX/SPF/DKIM/DMARC health check), quotas (mailboxes + redirections + per-mailbox disk), admin user, parent kSuite link, FQDN list, and team access flag. Use this for mail-config sanity checks. Manager-private.

  • infomaniak_get_mailbox_full

    Full mailbox detail: auto-responder (vacation reply) state + content, aliases, redirections, IMAP/POP3 last login, password age, size on disk, trusted devices count, DKIM signature flag, SMTP ban status, Gmail-style filtering (commercials/social_networks), authorized/blocked senders, attached users + teams. Useful for mailbox audits and onboarding flows. Manager-private.

  • infomaniak_get_mailbox_info

    Read mailbox metadata in one call. Pick any subset of {aliases, signatures, backups} via the `fields` argument; the tool hits only the corresponding endpoints in parallel. Replaces the v0.9 trio `get_mailbox_aliases` / `get_mailbox_signatures` / `get_mailbox_backups` with no loss of capability.

  • infomaniak_get_my_profile

    Get the identity of the currently-authenticated Infomaniak user: name, email, language, country, timezone, current_account_id (= the organization being managed by default), and the full security posture (2FA status, recovery email, validated phone, trusted devices, last login). Use this first to confirm which user + account the MCP is acting on behalf of. Manager-private \u2014 requires SASESSION

  • infomaniak_get_my_security

    Security posture report for the current user: 2FA status & method, recovery email, validated phone, Yubikey, remaining rescue codes, last login timestamp, password age, and the list of trusted (auth-paired) devices with their last connection IP and time. Useful as a periodic security review or pre-action sanity check. Manager-private.

  • infomaniak_get_nodejs_app

    Get full configuration of a Node.js application: Node version, listen port, start_command, build_command, public IPs (v4 + v6), SSL status, primary FQDN, preview URL, directory on disk, and disk usage. Manager-private \u2014 requires SASESSION + CSRF cookies.

  • infomaniak_get_vps_full

    Full VPS / Cloud Server detail: location (datacenter), managed/lite flags, IPv4 + IPv6, CPU/RAM/perf, bandwidth + traffic, disk usage (total/assigned/used/database), website/hosting counts, MySQL version + database type, PHP versions, firewall config, premium support contacts (email/url/emergency), migration history. Use after `infomaniak_list_vps` to drill into one server. Manager-private.

  • infomaniak_help

    Suggest which Infomaniak tools to use for a given intent expressed in natural language. Lightweight keyword matching against tool names and descriptions.

  • infomaniak_history

    List the destructive actions taken in the current session, most recent first. Each entry includes whether it can be reversed via infomaniak_undo.

  • infomaniak_list_ai_models

    List the public catalogue of LLM/STT/embedding models hosted by Infomaniak (Mixtral, Llama variants, Whisper, \u2026). Useful to know what to target with the OpenAI-compatible chat endpoint.

  • infomaniak_list_ai_products

    List the Infomaniak AI products the account owns. If empty, the user has not subscribed to any AI plan; subscribe at https://www.infomaniak.com/en/hosting/ai-tools.

  • infomaniak_list_database_users

    List the MariaDB-level user accounts attached to a web hosting (each has its own password and a `permissions` array listing the databases they can read/write/administer). For WordPress sites the user account has the same name as its database and is marked `protected: true`.

  • infomaniak_list_databases

    List every MariaDB database attached to a web hosting (with disk usage and any running operations).

  • infomaniak_list_domains

    List every domain owned by an Infomaniak organization, with creation and expiration dates.

  • infomaniak_list_drive_files

    List files and subfolders of a kDrive root or a specific folder. Supports pagination.

  • infomaniak_list_drive_trash

    List the items currently in the kDrive trash bin (files and folders). Each item shows when it was deleted and when added to the drive. Use this to audit what's pending hard-deletion. Manager-private.

  • infomaniak_list_drive_users

    List the users with access to a kDrive. Useful for access audits \u2014 who can touch what's in this drive. Manager-private.

  • infomaniak_list_drives

    List every kDrive the account has access to.

  • infomaniak_list_hosting_users

    List the FTP / SSH users that have access to a web hosting (with environment and SSH flag).

  • infomaniak_list_hostings

    Lists web hostings (classic + Node.js) for a given Infomaniak organization. Use infomaniak_list_organizations first to discover account IDs.

  • infomaniak_list_mail_hostings

    List every mail hosting (a.k.a. email_hosting) attached to an Infomaniak organization.

  • infomaniak_list_mailboxes

    List every mailbox on a given mail hosting.

  • infomaniak_list_nodejs_apps

    List Node.js applications running on a web hosting. Returns `site_id` + `vhost_route_id` for each app \u2014 both are needed for every other nodejs_* tool. Each Infomaniak Node.js hosting runs a single app, so this typically returns one entry. Uses the public Bearer API (more resilient than manager-private during Infomaniak maintenance).

  • infomaniak_list_organizations

    Lists all Infomaniak organizations (accounts) the current token has technical access to.

  • infomaniak_list_redirections

    List every server-side redirection rule on a mail hosting.

  • infomaniak_list_short_urls

    List the short URLs created by your account on Infomaniak's url-shortener service.

  • infomaniak_list_site_aliases

    List the FQDNs (main + aliases) bound to a web hosting site. The site responds to all of them via the same Apache vhost / DocumentRoot \u2014 adding an alias is how you serve more domains from a single WordPress install without provisioning a new site. Manager-private.

  • infomaniak_list_sites

    Lists all sites on a given web hosting (with applications attached).

  • infomaniak_list_swiss_backups

    List Swiss Backup subscriptions on an Infomaniak organization (Acronis-based managed backup).

  • infomaniak_list_teams_and_tags

    List the teams (with owners + user/product counts) AND the tags (with products carrying each tag) of an organization, in a single call. Both are useful to understand how an org partitions access and labels its products. Manager-private.

  • infomaniak_list_vps

    List the VPS (Cloud Server, Jelastic-managed) products of an organization. Returns id, customer_name, internal_name (the server hostname), location, cloud_version, managed/lite flags, billing. Use this before `infomaniak_get_vps_full` to find the id of a specific server. Manager-private.

  • infomaniak_manage_dnssec

    Unified DNSSEC management for a domain: `check` (read state + KSK/DS records), `enable` (publish DS record at registry), or `disable` (remove DS record). `enable` and `disable` use a two-phase commit: the first call returns a plan + confirmation_token (TTL ~60s), the second call applies the change. Replaces the v0.9 trio `dnssec_check` / `dnssec_enable` / `dnssec_disable` with no loss of capabilit

  • infomaniak_nodejs_app_action

    Start, stop, restart, or build a Node.js application. Two-phase commit: first call returns a plan + token, second call (with the token + same args) applies. `stop` causes downtime until next start. `build` triggers a build job and returns its log_stream so you can tail the output. Manager-private.

  • infomaniak_nodejs_app_aliases

    List the FQDNs (domain names) serving a Node.js application. Returns the primary FQDN plus the automatic preview URL (xxx.preview.hosting-ik.com). Manager-private.

  • infomaniak_nodejs_app_jobs

    List the recent jobs that ran for a Node.js app (builds, restarts, etc.) with their status and a JWT-protected log_stream endpoint per job. Manager-private.

  • infomaniak_nodejs_app_logs

    Get credentials to consume the LIVE stdout/stderr stream of a Node.js application. Returns a one-shot JWT (valid ~1h) and the endpoint URL on `manager-logs-01.hosting-ik.com`. The stream itself is Server-Sent Events: consume with `curl -N -H 'Authorization: Bearer <jwt>' <endpoint>`. To fetch a single snapshot, kill the curl after a few lines. Manager-private.

  • infomaniak_nodejs_app_status

    Get the live status of a Node.js application \u2014 `Running` or `Stopped`. Cheap call, safe to poll. Manager-private \u2014 requires SASESSION + CSRF cookies.

  • infomaniak_nodejs_app_thumbnail

    Get a screenshot of the running Node.js app as a base64 JPEG data URL. Useful to visually confirm the app is alive without HTTP-probing. Set `refresh=true` to force a fresh screenshot. Manager-private.

  • infomaniak_overview

    Returns a summary of all Infomaniak organizations and products you have access to. Best called first in a session.

  • infomaniak_provision_site_full

    Provision a complete website end-to-end: web site + MariaDB database + DNS A record. Two-phase commit at the workflow level. The plan lists every step that will run; on apply, each step is executed and reported in order so you can see partial completion if anything fails mid-way.

  • infomaniak_request_certificate

    Request a new SSL certificate (or re-issue / renew an existing one) for a site on a web hosting. Two-phase commit. Three types supported: `free` (Let's Encrypt, no extra fields), `paid` (Sectigo, requires `certificate_id`), `custom` (BYO PEM, requires `certificate` + `private_key`). Returns an `operation_uuid`; poll `infomaniak_get_certificate` to track progress.

  • infomaniak_short_urls_quota

    Return the current consumption and limit of your account's short-URL quota.

  • infomaniak_undo

    Reverse a destructive action recorded in the session history (when reversible). Two-phase commit: returns a plan first, then applies the undo on the second call.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

2 medium
  • Code scan3 source files scanned15/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 12 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10

Findings (2)

  • mediumnpm install lifecycle script presentinstall.script
  • mediumnpm install lifecycle script presentinstall.script
    package.json: … && npm run test && npm run build", "postinstall": "node scripts/postinstall.cjs || true" …
Overall 66/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Infomaniak Agent compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
66/100
higher than 28% of 4,461 AI and agents servers
Tools
78
the typical AI and agents server has 6
Tools that change things
23%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
8
more than 82% of 2,713 AI and agents servers

What its tools let an agent do: 60 read · 18 change

Install Infomaniak Agent in Claude Code, Cursor or VS Code

Runs npx -y infomaniak-mcp-agent on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add infomaniak-mcp-agent -- npx -y infomaniak-mcp-agent
Add to Cursor

What the publisher says

From the Infomaniak Agent repository's README, as published. We do not edit it. Read it on GitHub

infomaniak-mcp-agent

Drive your entire Infomaniak account from Claude — agentic, two-phase commit, open-source.

infomaniak-mcp-agent is an unofficial Model Context Protocol server that exposes the full surface of Infomaniak — Switzerland's sovereign cloud — as 78 tools an LLM can call directly: web hosting, mail (kSuite), kDrive, domains, DNS, DNSSEC, FTP/SSH users, AI products, account audits and more. Every destructive operation goes through a strict two-phase commit, so an agent can never silently delete or mutate something on your account.

You → Claude:  "audit the example.com hosting and tell me which mailboxes are over quota"
Claude → MCP:  infomaniak_audit_account → infomaniak_list_mail_hostings → infomaniak_list_mailboxes
Claude → You:  3 mailboxes >85% — paul@ (94%), notify@ (88%), team@ (87%). Want me to add an alert?

Table of contents

  • Why · What it does · How it differs
  • Install · Authentication · Quick example
  • Tools (78 across 22 areas) · Limitations · Roadmap · FAQ
  • Contributing · License

Why this exists

Infomaniak is one of the very few independent, Swiss-owned, open-source-friendly cloud providers in Europe — running its own datacentres in Switzerland, on hydro and wind power, with no parent in the US or China. Its product range is huge (web hosting, mail, kDrive, kChat, DNS, AI cloud, Swiss Backup, …) but its API is split between a documented public surface and a private manager-only one — which means automating real workflows usually requires a browser session, custom scripts, or both.

This project closes that gap by exposing everything through a single MCP server, so Claude or any other MCP client can run real account operations through natural language: provision a hosting, rotate a DNS record, create a mailbox, audit your domains for upcoming expirations, browse your kDrive — without ever forcing you to leave the chat or write a script.

🎒 Built in the open, in real time, by vibe-coding

This project was built rapidly by an LLM driving a terminal session ("vibe-coding"), with live tests against a real Infomaniak account at every step. It works perfectly on the maintainer's local setup and the full pipeline is green (TypeScript strict, ESLint, Prettier, 78 tests, build, CodeQL, gitleaks).

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Infomaniak Agent: common questions

Is Infomaniak Agent MCP server safe?
With care: it is graded C, so read the findings first (66/100). Read the Infomaniak Agent safety report
How do I install Infomaniak Agent?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Infomaniak Agent need an API key?
Yes. The registry entry asks for INFOMANIAK_API_TOKEN, INFOMANIAK_SASESSION, INFOMANIAK_XSRF_TOKEN.
Is Infomaniak Agent maintained?
The last commit was 52 days ago (2026-09-14). The latest release is v0.15.1.
How does Infomaniak Agent compare with other AI and agents MCP servers?
safety score 66/100 (higher than 28% of 4,461 AI and agents servers); tools 78 (the typical AI and agents server has 6); tools that change things 23% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.