infomaniak-admin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFOMANIAK_API_TOKEN | Yes | Bearer token for api.infomaniak.com. Required for all operations. | |
| INFOMANIAK_AUTH_MODE | No | Authentication mode: 'auto' (default) reads cookies from Chrome, 'manual' requires INFOMANIAK_SASESSION and INFOMANIAK_XSRF_TOKEN. | auto |
| INFOMANIAK_SASESSION | No | SASESSION cookie from manager.infomaniak.com. Required when INFOMANIAK_AUTH_MODE is manual. | |
| INFOMANIAK_XSRF_TOKEN | No | MANAGER-XSRF-TOKEN cookie from manager.infomaniak.com. Required when INFOMANIAK_AUTH_MODE is manual. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| infomaniak_overviewA | Returns a summary of all Infomaniak organizations and products you have access to. Best called first in a session. |
| infomaniak_tool_catalogA | List the MCP's Infomaniak tools by admin category, risk, and capability. Best for asking 'what can this MCP do?' before choosing a specific workflow. |
| infomaniak_helpA | Suggest which Infomaniak tools to use for a given intent expressed in natural language. Lightweight keyword matching against tool names and descriptions. |
| infomaniak_explainB | Returns the full definition of a specific tool — description, annotations, input parameters and output shape. |
| infomaniak_audit_accountA | Scan an Infomaniak organization for actionable issues: products expiring soon, products in maintenance, locked products, ongoing operations. |
| infomaniak_api_coverage_reportA | Fetch the Infomaniak developer portal navigation and report MCP endpoint coverage, admin candidates, risky writes, and user-focused surfaces that are intentionally out of scope. |
| infomaniak_audit_log_tailA | Read the newest entries from the persistent MCP audit log. Use this to inspect recent tool calls, write confirmations, applied changes, and failures. |
| infomaniak_audit_log_searchA | Search the persistent MCP audit log by tool name, phase, risk, timestamp range, or free text. Useful for answering 'what changed today?' and 'did anything destructive run?' |
| infomaniak_audit_dns_zonesA | Bulk-read every domain owned by an account: number of DNS records and DNSSEC status per zone. Useful for spot-checking large fleets. |
| infomaniak_historyA | List the destructive actions taken in the current session, most recent first. Each entry includes whether it can be reversed via infomaniak_undo. |
| infomaniak_undoA | 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. |
| infomaniak_get_my_profileA | 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 — requires SASESSION cookie. |
| infomaniak_get_my_securityA | 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_provision_site_fullA | 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_list_organizationsA | Lists all Infomaniak organizations (accounts) the current token has technical access to. |
| infomaniak_get_account_fullA | 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_list_teams_and_tagsA | 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_account_usersA | List users attached to an Infomaniak account. Read-only admin inventory for access review and offboarding. |
| infomaniak_get_user_app_accessesA | List app accesses for one account user. Read-only admin inventory for access audit and offboarding planning. |
| infomaniak_plan_user_offboardingA | Build a read-only initial offboarding plan for one account user from app accesses and invitations. This does not revoke anything. |
| infomaniak_audit_account_accessA | Read-only admin audit of account users and their app accesses. Highlights privileged access, broad access, and per-user fetch errors. |
| infomaniak_cancel_user_pending_invitationsA | Cancel pending account invitations for a user. Two-phase commit: first call returns the pending invitation list and confirmation token; second call deletes only invitations still pending in the fresh apply prefetch. |
| infomaniak_get_account_invitation_accessA | Inspect a single account invitation and its current access snapshot before granting or revoking kSuite, drive, mailbox, or kChat access. |
| infomaniak_manage_account_invitation_accessB | Grant, update, invite, or revoke invitation-scoped product access for kSuite, drive, mailbox, or kChat. Two-phase confirmation with a fresh invitation snapshot guard. |
| infomaniak_create_account_invitationA | Create an account invitation. Two-phase commit with a fresh account snapshot guard. The payload is passed through to Infomaniak as-is. |
| infomaniak_update_account_invitationA | Patch an account invitation. Two-phase commit with a fresh invitation snapshot guard. |
| infomaniak_delete_account_invitationA | Delete an account invitation. Two-phase commit with a fresh invitation snapshot guard. |
| infomaniak_create_account_teamA | Create an account team. Two-phase commit with a fresh team list snapshot guard. The payload is passed through to Infomaniak as-is. |
| infomaniak_update_account_teamB | Update an account team. Two-phase commit with a fresh team snapshot guard. |
| infomaniak_delete_account_teamA | Delete an account team. Two-phase commit with a fresh team snapshot guard. |
| infomaniak_add_account_team_usersA | Add one or more users to an account team. Two-phase commit with a fresh team-members snapshot guard. |
| infomaniak_remove_account_team_usersA | Remove one or more users from an account team. Two-phase commit with a fresh team-members snapshot guard. |
| infomaniak_create_account_tagA | Create an account tag. Two-phase commit with a fresh tag-list snapshot guard. The payload is passed through to Infomaniak as-is. |
| infomaniak_update_account_tagA | Update an account tag. Two-phase commit with a fresh tag snapshot guard. |
| infomaniak_delete_account_tagA | Delete an account tag. Two-phase commit with a fresh tag snapshot guard. |
| infomaniak_get_account_resourcesB | Read account inventory and governance drill-down resources: accounts, products, services, tags, basic teams, team members, and B2B invitation customers. |
| infomaniak_manage_account_invitation_b2bA | Assign or unassign B2B customer partnerships on an account invitation. Two-phase confirmation with a fresh partnership snapshot. |
| infomaniak_list_hostingsA | Lists web hostings (classic + Node.js) for a given Infomaniak organization. Use infomaniak_list_organizations first to discover account IDs. |
| infomaniak_list_domainsA | List every domain owned by an Infomaniak organization, with creation and expiration dates. |
| infomaniak_get_domainA | Get detailed information about a domain (DNS management status, DNSSEC, IDN, errors). |
| infomaniak_get_domain_fullA | 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_domain_resourcesC | Read canonical v2 domain, zone, DNSSEC, and DNS-record resources from the Infomaniak public API. |
| infomaniak_manage_domain_nameserversA | Update a domain's nameservers or restore Infomaniak nameservers. Two-phase confirmation with a current domain snapshot. |
| infomaniak_find_siteA | 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 first match. |
| infomaniak_list_sitesA | Lists all sites on a given web hosting (with applications attached). |
| infomaniak_create_siteA | 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_siteA | 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_list_site_aliasesA | List the FQDNs (main + aliases) bound to a web hosting site. The site responds to all of them via the same Apache vhost / DocumentRoot — adding an alias is how you serve more domains from a single WordPress install without provisioning a new site. Manager-private. |
| infomaniak_add_site_aliasesA | Bind one or more additional FQDNs (including wildcards like |
| infomaniak_delete_site_aliasA | 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_get_certificateA | Return the full SSL certificate detail for one site on a web hosting: provisioning state ( |
| infomaniak_request_certificateA | 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: |
| infomaniak_delete_certificateA | 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_list_databasesA | List every MariaDB database attached to a web hosting (with disk usage and any running operations). |
| infomaniak_get_databaseA | Get the full detail of a specific database (disk usage, application, permissions, backups). |
| infomaniak_create_databaseA | 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_delete_databaseA | 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_list_database_usersA | List the MariaDB-level user accounts attached to a web hosting (each has its own password and a |
| infomaniak_get_database_userA | Fetch the detail of a single MariaDB-level user (applications, permissions, link to phpMyAdmin). |
| infomaniak_list_hosting_usersA | List the FTP / SSH users that have access to a web hosting (with environment and SSH flag). |
| infomaniak_create_hosting_userA | Create a new FTP / SSH user on a web hosting. Two-phase commit. Connection types: |
| infomaniak_delete_hosting_userA | Revoke a hosting user (FTP / SSH access). Two-phase commit. Existing files are not deleted. |
| infomaniak_dns_list_recordsA | List every DNS record on a zone managed by Infomaniak. Use the root domain (e.g. 'example.com'), not a subdomain. |
| infomaniak_dns_create_recordA | 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_update_recordA | 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_dns_delete_recordA | 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_audit_domain_dns_adminA | Read-only domain/DNS admin posture audit: DNSSEC, MX, SPF, DMARC, wildcard records, and very low TTLs for an Infomaniak-managed zone. |
| infomaniak_manage_dnssecA | Unified DNSSEC management for a domain: |
| infomaniak_list_mail_hostingsA | List every mail hosting (a.k.a. email_hosting) attached to an Infomaniak organization. |
| infomaniak_list_mailboxesA | List every mailbox on a given mail hosting. |
| infomaniak_get_mailbox_infoA | Read mailbox metadata in one call. Pick any subset of {aliases, signatures, backups} via the |
| infomaniak_get_mailbox_securityA | Read mailbox security and spam-control state: authorized senders, blocked senders, spam move policy, mail filtering folders, and note. |
| infomaniak_list_mailbox_filtersA | List Sieve filters, scripts, and available templates for a mailbox. Read-only admin inventory for spam/filter policy auditing. |
| infomaniak_list_mailbox_filter_scriptsA | List only the advanced Sieve scripts configured on a mailbox. Focused read-only view derived from the mailbox filter inventory endpoint. |
| infomaniak_audit_mailbox_securityA | Read-only admin audit for a mailbox security posture: spam policy, sender conflicts, Sieve scripts, and disabled filters. |
| infomaniak_get_mail_hosting_fullA | 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_fullA | 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_mail_signaturesA | Inspect mailbox signatures and signature templates at the mailbox or service level. Read-only inventory for admin review and template selection. |
| infomaniak_get_mail_webmail_accessA | Inspect mailbox webmail access for users and teams, plus admin audit lookups for account-scoped access records. Read-only inventory for webmail governance. |
| infomaniak_get_mail_device_accessA | Inspect mailbox device/session access for a selected mailbox user, or list mailbox/service device inventories for cleanup planning. |
| infomaniak_create_mailboxA | 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_delete_mailboxA | Delete a mailbox. Two-phase commit. WARNING: this also deletes all stored emails for that mailbox. |
| infomaniak_create_mailbox_aliasA | Add a new alias to an existing mailbox. Two-phase commit. The alias will receive emails delivered to the underlying mailbox. |
| infomaniak_block_senderA | Block this sender. Two-phase commit: first call returns the current-state diff and confirmation token, second call with the token applies the PATCH if the mailbox sender lists have not changed. |
| infomaniak_unblock_senderA | Unblock this sender. Two-phase commit: first call returns the current-state diff and confirmation token, second call with the token applies the PATCH if the mailbox sender lists have not changed. |
| infomaniak_authorize_senderA | Authorize this sender. Two-phase commit: first call returns the current-state diff and confirmation token, second call with the token applies the PATCH if the mailbox sender lists have not changed. |
| infomaniak_unauthorize_senderA | Remove this authorized sender. Two-phase commit: first call returns the current-state diff and confirmation token, second call with the token applies the PATCH if the mailbox sender lists have not changed. |
| infomaniak_set_mailbox_spam_policyA | Update mailbox spam movement, smart filtering folders, and admin note. Two-phase commit: returns a current-state diff and confirmation token, then applies only if the policy state has not changed. |
| infomaniak_harden_mailbox_securityA | Plan and apply conservative mailbox security hardening: enable spam movement, enable mail filtering, and optionally set filtering folders. Two-phase commit with audit/current-state guard. |
| infomaniak_update_mailbox_foldersA | Update mailbox folder mappings for archives, drafts, sent, trash, spam, commercials, and social-network folders. Two-phase commit with mailbox security state guard. |
| infomaniak_purge_spam_folderA | Delete all messages currently in a mailbox spam folder. Destructive two-phase commit with mailbox security state guard. |
| infomaniak_create_mailbox_filterA | Create a mailbox Sieve filter. Two-phase commit: first call returns current filter inventory and confirmation token, second call applies the POST if inventory is unchanged. |
| infomaniak_update_mailbox_filterA | Update or rename a mailbox Sieve filter. Two-phase commit with current filter inventory guard before PATCH. |
| infomaniak_delete_mailbox_filterA | Delete a mailbox Sieve filter by name. Two-phase commit with current filter inventory guard before DELETE. |
| infomaniak_upsert_mailbox_filter_scriptA | Create or update a mailbox Sieve script. Omit old_name to create; provide old_name to update/rename. Two-phase commit with current inventory guard. |
| infomaniak_delete_mailbox_filter_scriptA | Delete a mailbox Sieve script by name. Two-phase commit with current filter/script inventory guard before DELETE. |
| infomaniak_list_email_importsA | List email-import jobs and their state for a mailbox. |
| infomaniak_manage_mailbox_filter_lifecycleA | Enable/disable mailbox filters or Sieve scripts, or reorder filters. All changes use two-phase confirmation with a fresh filter snapshot. |
| infomaniak_empty_mailbox_trashA | Permanently delete all messages in a mailbox trash folder after confirmation. |
| infomaniak_list_mailing_listsA | List mailing lists configured on a mail hosting. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/henrikogaard/infomaniak-admin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server