Skip to main content
Glama

calendar-tasks-mcp

An MCP server that lets Claude manage the workshop@burrowsjewellers.com.au Outlook calendar and Microsoft To Do, via Microsoft Graph. Built as a sibling to burrows-mcp, in the dashboard's Node/ESM style, with the same token-lifecycle pattern as xeroClient.js (mint once → silent refresh, refresh token stored in Postgres).

Delegated, least-privilege: it signs in as workshop@ and can only touch that mailbox's calendar and tasks — no mail, no files.

Tools

Tool

What it does

create_event

Create a calendar event (local wall-clock time + timezone), with a phone reminder.

update_event

Change fields on an event by id.

delete_event

Delete one event by id.

find_events

List events in a window (resolve an id before update/delete).

create_task

Add a task to the "Burrows Ops" To Do list (due date + reminder optional).

complete_task

Mark a task complete.

find_tasks

List tasks (resolve an id before completing).

The agent is instructed (via tool descriptions) to confirm before deleting events or acting on many items at once — this is write access to a live calendar.


Related MCP server: Outlook MCP Server

One-time setup

1. Register the Entra (Azure AD) app

In the Entra admin center → Identity → Applications → App registrations → New registration:

  1. Name: burrows-calendar-tasks-mcp

  2. Supported account types: Accounts in this organizational directory only (single tenant).

  3. Register. Copy the Application (client) ID and Directory (tenant) ID → these become GRAPH_CLIENT_ID / GRAPH_TENANT_ID.

  4. Authentication → Advanced settings → Allow public client flows → Yes. (Device-code flow needs this; no client secret is created.)

  5. API permissions → Add a permission → Microsoft Graph → Delegated permissions, add exactly:

    • Calendars.ReadWrite

    • Tasks.ReadWrite

    • offline_access

    • User.Read

  6. Grant admin consent (button at the top) using the Global Admin adm_mark.burrows@…onmicrosoft.com.

2. Configure

cp .env.example .env
# set GRAPH_CLIENT_ID, GRAPH_TENANT_ID, confirm GRAPH_DEFAULT_TIMEZONE, fill PG* for the token table
npm install

3. Sign in once (mint the refresh token)

npm run login

Open the printed URL, enter the code, and sign in as workshop@burrowsjewellers.com.au. The refresh token is stored (Postgres graph_tokens table by default). After this the server refreshes access tokens silently.

4. (Optional) Verify live

npm run smoke    # creates + cleans up a test event and task against the real mailbox

Run / deploy

Locally, the MCP runs over stdio:

npm start

On the droplet, run it under pm2 like burrows-dashboard-api:

pm2 start src/server.js --name calendar-tasks-mcp --interpreter node
pm2 save

Register it with your MCP client (e.g. burrows-mcp's host config):

{
  "mcpServers": {
    "calendar-tasks": {
      "command": "node",
      "args": ["/path/to/calendar-tasks-mcp/src/server.js"]
    }
  }
}

Config (.env)

Key

Purpose

GRAPH_CLIENT_ID / GRAPH_TENANT_ID

From the Entra app registration.

GRAPH_DEFAULT_TIMEZONE

IANA tz applied to events/tasks. Confirm the store's timezone.

GRAPH_DEFAULT_REMINDER_MINUTES

Default event reminder lead time (30).

GRAPH_TODO_LIST_NAME

To Do list for tasks (Burrows Ops).

GRAPH_TOKEN_STORE

postgres (default) or file (local dev).

PGUSER/PGPASSWORD/PGHOST/PGPORT/PGDATABASE

Token table (reuses burrows_jewellers).

Tests

npm test     # payload-builder unit tests + a spawned-server integration test (no live Graph needed)

Notes / cautions

  • Reminders fire on the phone only if workshop@ is signed into the phone's Outlook app. Add it if not.

  • Conditional-access policies can occasionally force a fresh npm run login; the refresh token isn't guaranteed to last forever.

  • Token storage mirrors the dashboard's xero_tokens: one row, app-owned, never committed to git.

Available Tools

7 tools
complete_taskA

Mark a Microsoft To Do task complete by id.

Inputs: taskId (required), listName.

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.

Inputs: end (required), start (required), subject (required), body, +4 more.

create_taskB

Create a Microsoft To Do task in the "Burrows Ops" list (created on first use). Optional due date and reminder.

Inputs: title (required), body, dueDate, listName, +1 more.

delete_eventA

Delete a single calendar event by id. For deleting multiple events, confirm with the user first.

Inputs: eventId (required).

find_eventsA

List events between two datetimes (use this to resolve an event id before updating or deleting). start/end are ISO datetimes.

Inputs: end (required), start (required), timeZone.

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.

Inputs: status, listName.

update_eventA

Update an existing calendar event by id. Only the fields you pass are changed.

Inputs: eventId (required), end, body, start, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Related MCP Connectors

    Related MCP Servers