kalender.digital MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP mode (default is 3000) | |
| MCP_TRANSPORT | No | Transport mode, e.g., 'http' for HTTP mode. Default is stdio. | |
| MCP_ALLOWED_ORIGINS | No | Comma-separated allowed origins for HTTP mode (e.g., https://claude.ai,https://chatgpt.com) | |
| KALENDER_DIGITAL_API_KEY | Yes | Your kalender.digital API key from Admin Settings -> API |
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_eventsA | List kalender.digital events within an inclusive date range, optionally filtered by a search query. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| get_eventA | Fetch one kalender.digital event by its event ID. Use list_events if the ID is unknown. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| create_eventA | Create an event in one or more kalender.digital subcalendars. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| update_eventA | Replace the editable fields of an existing kalender.digital event. All event fields are required. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| delete_eventA | Permanently delete a kalender.digital event by ID. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| create_subcalendarA | Create a kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| update_subcalendarB | Rename an existing kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de |
| delete_subcalendarA | Permanently delete a kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de |
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 targets either an event or a subcalendar resource with a unique action. No two tools could be confused, as event tools handle event lifecycle and subcalendar tools handle subcalendar lifecycle.
All tools follow a consistent verb_noun pattern with snake_case (create_, update_, delete_, list_events, get_event). The naming is uniform and predictable across both resource types.
Eight tools is well-scoped for a calendar server, covering events and subcalendars without unnecessary bloat. Each tool serves a clear purpose within the domain.
Events have full CRUD plus list coverage, but subcalendars lack list and get operations. This is a notable gap because agents cannot discover existing subcalendars to assign events to, limiting workflow completion.