jmap-calendar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JMAP_SESSION_URL | Yes | The server's JMAP session URL, usually https://<host>/.well-known/jmap | |
| JMAP_BEARER_TOKEN | Yes | API key for the account | |
| JMAP_ALLOW_INVITES | No | Set to 1 to allow sending invitations when a call asks for it; off by default |
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_calendarsA | List the calendars this account can see, with which is the default. |
| find_calendar_eventsA | Find events between two times (default: the next 30 days), optionally matching text. Recurring events are expanded into their occurrences. |
| create_calendar_eventA | Create an event. Confirm title, time and time zone with the user first. Attendees are added without being emailed unless send_invitations is true. |
| update_calendar_eventA | Change an existing event: give event_id and only the fields to change. |
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
Each tool has a clearly distinct purpose: listing calendars, finding events, creating events, and updating events. There is little risk of confusing list_calendars with event search, or create_calendar_event with update_calendar_event.
All tool names use a consistent snake_case verb_noun pattern: list_calendars, find_calendar_events, create_calendar_event, update_calendar_event. The convention is predictable across the entire set.
Four tools is a well-scoped set for a focused calendar MCP server, with each tool covering a distinct operation. It stays lean without feeling arbitrary.
The surface covers listing calendars, finding events, creating events, and updating events, but lacks a delete_event operation and lacks calendar management operations. These are notable lifecycle gaps, though the existing tools support core read/write workflows.