calendar-tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PGHOST | Yes | PostgreSQL host (for token table) | |
| PGPORT | Yes | PostgreSQL port (for token table) | |
| PGUSER | Yes | PostgreSQL user (for token table) | |
| PGDATABASE | Yes | PostgreSQL database name (for token table) | |
| PGPASSWORD | Yes | PostgreSQL password (for token table) | |
| GRAPH_CLIENT_ID | Yes | Application (client) ID from Entra app registration | |
| GRAPH_TENANT_ID | Yes | Directory (tenant) ID from Entra app registration | |
| GRAPH_TOKEN_STORE | No | Token storage method: 'postgres' or 'file' (default 'postgres') | postgres |
| GRAPH_TODO_LIST_NAME | No | To Do list name for tasks (default 'Burrows Ops') | Burrows Ops |
| GRAPH_DEFAULT_TIMEZONE | Yes | IANA timezone applied to events/tasks (e.g. 'Australia/Melbourne') | |
| GRAPH_DEFAULT_REMINDER_MINUTES | No | Default event reminder lead time in minutes (default 30) | 30 |
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 |
|---|---|
| create_eventA | Create an Outlook calendar event in the workshop@ mailbox. Times are local wall-clock (e.g. 2026-07-01T14:00:00), interpreted in the default timezone unless timeZone is given. Sets a phone reminder by default. |
| update_eventA | Update an existing calendar event by id. Only the fields you pass are changed. |
| delete_eventA | Delete a single calendar event by id. For deleting multiple events, confirm with the user first. |
| find_eventsA | List events between two datetimes (use this to resolve an event id before updating or deleting). start/end are ISO datetimes. |
| create_taskB | Create a Microsoft To Do task in the "Burrows Ops" list (created on first use). Optional due date and reminder. |
| complete_taskA | Mark a Microsoft To Do task complete by id. |
| find_tasksA | List tasks in the "Burrows Ops" list (use this to resolve a task id before completing it). Optional status filter: notStarted | inProgress | completed. |
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 7 tools
Tools are clearly split into calendar event and task domains, each with distinct verbs (create, find, update, delete for events; create, find, complete for tasks). No overlap or ambiguity.
All tool names use a consistent verb_noun pattern in snake_case (e.g., create_event, complete_task). The naming is predictable and follows a uniform style.
With 7 tools spanning two domains, the count is reasonable. It could include a few more (like update_task or delete_task), but the current set covers essential operations without being excessive.
Event tools provide full CRUD (create, find, update, delete). Task tools are missing update and delete operations, and lack an uncomplete action. This leaves gaps in task lifecycle management.