Infomaniak Contact MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTACT_TOKEN | Yes | Your Infomaniak API token with contacts scope |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| contact_listB | List all contacts from your Infomaniak account |
| contact_searchB | Search contacts by name, email, or phone |
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 2 tools
contact_list and contact_search are mostly distinct: one enumerates all contacts, the other filters by query. There is minor overlap since listing all contacts is a degenerate search, but an agent can reasonably choose between them.
Both tools follow a clear and consistent contact_verb pattern (contact_list, contact_search). The naming is predictable and easy to generalize.
Two tools is thin for a contact management server, which typically needs more operations. The count is not extreme, but it feels under-scoped for the domain.
The surface only supports reading and searching; there is no create, update, delete, or get-by-ID operation. This leaves significant gaps for any contact lifecycle workflow.