Infomaniak AI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFOMANIAK_API_TOKEN | No | Infomaniak API token used to start the server. Required unless INFOMANIAK_API_TOKEN_FILE is provided. | |
| INFOMANIAK_MCP_SHA256 | No | SHA256 checksum of the reviewed backend entry file for the original three-tool read-only edition. | |
| INFOMANIAK_API_TOKEN_FILE | No | Absolute path to a regular secret file (mode 0600) containing the Infomaniak API token. Do not set both token sources. | |
| INFOMANIAK_MCP_SERVER_PATH | No | Absolute path to the reviewed dist/server.js backend for the original three-tool read-only edition. |
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_statusC | Check catalogue coverage, connection policy and reviewed capabilities. |
| infomaniak_searchB | Discover public API operations. Catalogue entries may be unavailable; reviewed schemas load on demand. |
| infomaniak_catalogueB | Browse all public API metadata by product/method. Discovery does not grant execution. |
| infomaniak_readC | Call a reviewed read within this connection's account/resource grants. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
status and read are clearly distinct (policy check vs. executing a reviewed read). search and catalogue both address API metadata discovery and could be confused, though the descriptions hint at different scopes (operation discovery vs. browsing by product/method).
All four tools use the same infomaniak_ prefix with snake_case suffixes. The pattern is entirely predictable across the set.
Four tools is reasonable for a discovery-plus-read server. Slightly thin, but each tool maps to a distinct capability (status, search, browse, execute read).
The surface is intentionally read-only with discovery, so no mutation/execution tools exist. This covers metadata lookup and reads but leaves a notable gap for any write workflow, which agents cannot work around.