pim-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIM_MCP_CONFIG | No | Path to an alternative config file. The config lives at ~/.config/pim-mcp/config.toml by default on every OS (C:\Users\<you>\.config\pim-mcp\config.toml on Windows). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_calendarsA | List every calendar across all configured accounts (Nextcloud, iCloud, Google, …), with ids usable in other tools. |
| list_eventsA | Events in a time range, merged across all calendars and sorted by start. Recurring events are expanded into occurrences. Defaults to today through the next 7 days. |
| search_eventsA | Find events whose title, location or description contains the query (case-insensitive). Defaults to 90 days back through 365 days ahead. |
| get_eventB | Full details of one event (description, attendees, organizer, recurrence rule). |
| find_free_timeA | Free time windows of at least |
| create_eventA | Create an event. |
| update_eventA | Change an event. Only the fields you pass change; moving |
| delete_eventA | Delete an event. For recurring events pass |
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 8 tools
Each tool maps to a distinct retrieval or mutation strategy: list_events filters by time range, search_events filters by text query, and get_event fetches a single event by id. find_free_time and the create/update/delete trio are unmistakable. No two tools overlap in a way that would cause misselection.
All eight tools follow the same snake_case verb_noun pattern (list_, search_, get_, find_, create_, update_, delete_). The verb choice matches the operation type consistently, and the resource noun is always the trailing token.
Eight tools is well within the healthy 3-15 range and every tool earns its place: discovery, three read modes, availability lookup, and full mutation coverage. Nothing feels padded or redundant.
Event lifecycle is fully covered (list/search/get/create/update/delete) with sensible recurrence scope and availability handling. Minor gaps remain around attendee interactions — no RSVP/accept-decline tool and calendars themselves can only be listed, not created or modified.