@mindstone/mcp-server-microsoft-calendar

Microsoft 365 Outlook Calendar MCP server — list, get, create, update, delete, cancel, and respond to events, check free/busy, find meeting times, and list calendars via the Microsoft Graph API.

Cohort-style Microsoft 365 calendar MCP. Reuses the OAuth surface owned by @mindstone/mcp-server-microsoft-mail so the host signs in once and gets calendar plus mail plus files plus Teams plus SharePoint from the same credentials.

Status

• Version: 0.2.0 · npm
• Auth: OAuth (host-orchestrated, shared with mcp-server-microsoft-mail) (MS_CLIENT_ID)
• Tools: 10 (events, calendars, free-busy, scheduling)
• Surface: cloud-api
• Machine-readable: STATUS.json
• Shared library: @mindstone/mcp-server-microsoft-shared

Why this exists

When we ported this in May 2026, Microsoft's own Graph MCP lineup did not yet ship a stand-alone Outlook Calendar server, and the community options at the time treated calendar as its own login surface — every connector ran a separate OAuth dance and stored its own copy of the refresh token. We pulled the bundled connector out of MindstoneRebel as a 1:1 port so that the same five-connector Microsoft 365 cohort (mail, calendar, files, teams, SharePoint) shares a single set of credentials, a single shared-library package for token persistence and request timeouts, and the structured auth_required envelope the host already knows how to recover from. Calendar reuses @mindstone/mcp-server-microsoft-mail's authenticate_microsoft_account tool rather than declaring its own.

Example interaction

"What's on my calendar this afternoon, and find a 30-minute slot tomorrow when both Alice and I are free."

Tools the host calls:

1. list_events — date range covering the rest of today.
2. find_meeting_times — suggests slots tomorrow when both Alice and the user are free.

Response (trimmed):

{
  "today": [
    { "id": "AA...=", "subject": "Q3 review", "start": "2026-05-19T15:00:00Z", "end": "2026-05-19T16:00:00Z" }
  ],
  "tomorrow_suggestions": [
    { "start": "2026-05-20T10:00:00", "end": "2026-05-20T10:30:00" },
    { "start": "2026-05-20T14:30:00", "end": "2026-05-20T15:00:00" }
  ]
}

Requirements

• Node.js 20+
• npm
• A host application that performs the Microsoft OAuth flow and writes per-account token files into ${MS_CONFIG_DIR}/credentials/${sanitised-email}.token.json and an ${MS_CONFIG_DIR}/accounts.json index. This server reads those files; it does not initiate OAuth itself.

One-click install

After clicking the button, your host will prompt you to fill: MS_CLIENT_ID, MS_CONFIG_DIR, MS_MCP_PACKAGE_ID, MICROSOFT_REQUEST_TIMEOUT_MS.

{
  "mcpServers": {
    "Microsoft 365 Calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-microsoft-calendar"
      ],
      "env": {
        "MS_CLIENT_ID": "",
        "MS_CONFIG_DIR": "",
        "MS_MCP_PACKAGE_ID": "Microsoft365Calendar",
        "MICROSOFT_REQUEST_TIMEOUT_MS": "60000"
      }
    }
  }
}

Quick Start

Install & build

cd <path-to-repo>/connectors/microsoft-calendar
npm install
npm run build

npx (once published)

npx -y @mindstone/mcp-server-microsoft-calendar

Local

node dist/index.js

Configuration

This server runs alongside a host application that owns the Microsoft 365 OAuth flow. The host writes credentials to disk; this server reads them.

Required environment variables

Optional environment variables

Host configuration examples

Claude Desktop / Cursor

{
  "mcpServers": {
    "Microsoft365Calendar": {
      "command": "npx",
      "args": ["-y", "@mindstone/mcp-server-microsoft-calendar"],
      "env": {
        "MS_CLIENT_ID": "your-entra-application-client-id",
        "MS_CONFIG_DIR": "/absolute/path/to/microsoft-config"
      }
    }
  }
}

Sign in via @mindstone/mcp-server-microsoft-mail's authenticate_microsoft_account first; the calendar tools then reuse the credentials it writes to ${MS_CONFIG_DIR}/.

Local development (no npm publish needed)

{
  "mcpServers": {
    "Microsoft365Calendar": {
      "command": "node",
      "args": ["<path-to-repo>/connectors/microsoft-calendar/dist/index.js"],
      "env": {
        "MS_CLIENT_ID": "your-entra-application-client-id",
        "MS_CONFIG_DIR": "/absolute/path/to/microsoft-config"
      }
    }
  }
}

Tools (10)

Security notes

• No authentication tool of its own; sign-in is delegated to @mindstone/mcp-server-microsoft-mail so the cohort has a single OAuth surface.
• Token files are written by the host with mode 0600; this server reads them via the cohort-shared library, which fails closed on malformed files.
• MICROSOFT_DISABLE_REFRESH=1 is the default on cloud surfaces so the desktop session remains the sole refresh-token authority.
• Per-tool Graph calls run under a composed caller + cohort timeout signal.
• All Graph-sourced text is returned inside <untrusted-content> envelopes; structural-looking fields (IDs, URLs, enum-like values, timestamps) pass through raw only when they match their documented closed format and are enveloped otherwise. Vendor error messages are enveloped before they reach the model.
• Tool inputs are validated fail-closed (email addresses, ISO date-times, bounded numerics, strict recurrence objects) before any Graph request is made.
• Event/calendar IDs interpolated into Graph request paths are validated fail-closed (rejecting ?, #, %, \, whitespace, and ./.. segments) before any network request and URL-encoded at the interpolation site, so a crafted ID cannot reroute the authenticated request.
• Graph pagination is never silently dropped: list endpoints report truncated / attachmentsTruncated instead of following vendor-supplied continuation URLs.

Licence

FSL-1.1-MIT — Functional Source License, Version 1.1, with MIT future licence. Free for non-competing use; relicenses to MIT on the converter date in LICENSE.