honest-calendar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALENDAR_TOKEN_PATH | No | Per-account token file | token.json |
| CALENDAR_SERVER_NAME | No | MCP server name | calendar-personal |
| CALENDAR_CREDENTIALS_PATH | No | OAuth client (can be shared across accounts) | credentials.json |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_calendarsA | List all calendars available on this account with id, summary, and access role. |
| list_eventsA | List events in a calendar within a time range. Returns event id, summary, start, end, location, attendees. Default calendar is 'primary'. |
| get_eventC | Fetch full details of a single event by id. |
| create_eventC | Create a new event. Times as RFC3339 datetimes (timed) or YYYY-MM-DD (all-day). Attendees is a list of email strings. |
| update_eventB | Partial update of an existing event. Only pass the fields you want to change. Uses PATCH semantics. |
| delete_eventC | Delete an event by id. |
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 6 tools
Each tool targets a distinct resource and action: listing calendars vs. events, and get/create/update/delete for events. There is no overlap between any pair of tools, so an agent can select correctly without hesitation.
All names follow a strict snake_case verb_noun pattern: list_calendars, list_events, get_event, create_event, update_event, delete_event. There are no deviations in style or verb forms.
Six tools is well-scoped for a calendar server, covering the essential read/write/delete operations without bloat. Every tool has a clear place in the surface.
Event lifecycle is fully covered with list, get, create, update, and delete. Minor gaps exist such as no search/free-busy query and no calendar management beyond listing, but core calendar workflows are complete and workable.