infomaniak-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFOMANIAK_USER | Yes | Infomaniak account id (DAV username), e.g. AB12345. This is not the mailbox address. | |
| INFOMANIAK_DAV_URL | No | Base DAV server URL. | https://sync.infomaniak.com |
| INFOMANIAK_CALENDAR | No | Name of the calendar to use; defaults to the first one found. | |
| INFOMANIAK_ADDRESSBOOK | No | Name of the address book to use; defaults to the first one found. | |
| INFOMANIAK_APP_PASSWORD | Yes | Infomaniak application password generated from manager.infomaniak.com. |
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 |
|---|---|
| list_collectionsA | List the address books and calendars this account can reach. Useful when the account has more than one and you need the exact name. |
| search_contactsA | Search the address book by name, organisation, note, email or phone digits. Accent insensitive. |
| create_contactA | Add a contact. The write is read back and rolled back if the server altered it, so a success means the stored card matches what was sent. |
| list_eventsC | Upcoming calendar events. |
| create_eventA | Add a calendar event. Give start as 'YYYY-MM-DD HH:MM' for a timed event or 'YYYY-MM-DD' for an all day one. |
| delete_eventA | Delete a calendar event by its resource path, as returned by list_events. |
| list_tasksD | Reminders and tasks stored as VTODO on the calendar. |
| create_taskC | Add a reminder, optionally with a due date. |
| complete_taskA | Mark a reminder done by its resource path, as returned by list_tasks. |
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 9 tools
Each tool targets a distinct resource and action: collections, contacts, events, and tasks are cleanly separated. There is no meaningful overlap between search_contacts and the calendar/task operations.
All tools follow a consistent verb_noun pattern such as list_events, create_contact, delete_event. The naming is predictable and uniform across the entire surface.
Nine tools is well scoped for a contacts and calendar server. Each tool covers a clear need without unnecessary duplication or bloat.
The domain is covered for basic listing, creating, and in some cases deleting, but notable lifecycle gaps exist: contacts have no update or delete, events have no update, and tasks have no delete. Agents can accomplish core workflows but will hit dead ends when trying to modify existing contacts or rearrange events.