Skip to main content
Glama
Fastmail Calendar MCP Server

Fastmail Calendar MCP Server

by NOVA-3951

Fastmail Calendar MCP Server

An MCP (Model Context Protocol) server that enables AI assistants to interact with Fastmail Calendar via CalDAV. This allows AI to view, create, modify, and delete calendar events in your Fastmail account.

Features

  • List Calendars: View all calendars in your Fastmail account

  • List Events: Retrieve events from a specific calendar within a date range

  • Create Events: Add new calendar events with details like title, description, location, and time

  • Update Events: Modify existing calendar events

  • Delete Events: Remove calendar events

Related MCP server: caldav-mcp

Configuration

This MCP server requires the following configuration:

  • username: Your Fastmail email address (e.g., user@fastmail.com)

  • appPassword: A Fastmail app password (16 characters)

Creating a Fastmail App Password

  1. Log in to Fastmail

  2. Go to Settings → Privacy & Security → Integrations

  3. Click New app password

  4. Select permissions (ensure "Calendars" is included)

  5. Click Generate password

  6. Copy the generated password (16 characters)

Installation

Via Smithery

smithery install fastmail-calendar-mcp --client claude --config '{"username":"your-email@fastmail.com","appPassword":"your-app-password"}'

Manual Installation for Claude Desktop

Add to your Claude Desktop config file (~/.config/claude/claude_desktop_config.json):

{
  "mcpServers": {
    "fastmail-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "fastmail-calendar-mcp"
      ],
      "env": {
        "FASTMAIL_USERNAME": "your-email@fastmail.com",
        "FASTMAIL_APP_PASSWORD": "your-app-password"
      }
    }
  }
}

For Cursor IDE

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "fastmail-calendar": {
      "command": "node",
      "args": ["/path/to/fastmail-calendar-mcp/dist/index.js"],
      "env": {
        "FASTMAIL_USERNAME": "your-email@fastmail.com",
        "FASTMAIL_APP_PASSWORD": "your-app-password"
      }
    }
  }
}

Development

Setup

npm install
npm run build

Running Locally

export FASTMAIL_USERNAME="your-email@fastmail.com"
export FASTMAIL_APP_PASSWORD="your-app-password"
npm start

Development Mode

npm run dev

This will watch for changes and automatically rebuild.

Deploying to Smithery

  1. Push this repository to GitHub

  2. Go to smithery.ai

  3. Click Deploy

  4. Select your GitHub repository

  5. Smithery will automatically detect the TypeScript MCP project and deploy it

Available Tools

list_calendars

Lists all calendars in your Fastmail account.

Returns: Array of calendar objects with displayName, url, description, and timezone.

list_events

Lists events from a specific calendar within a date range.

Parameters:

  • calendarUrl (required): The URL of the calendar

  • startDate (required): Start date in ISO format (e.g., "2024-01-01")

  • endDate (required): End date in ISO format (e.g., "2024-12-31")

Returns: Array of event objects with url, etag, and data (iCalendar format).

create_event

Creates a new calendar event.

Parameters:

  • calendarUrl (required): The calendar URL where the event will be created

  • summary (required): Event title

  • startDate (required): Event start date/time in ISO format

  • endDate (required): Event end date/time in ISO format

  • description (optional): Event description

  • location (optional): Event location

Returns: Success message with the created event URL.

update_event

Updates an existing calendar event.

Parameters:

  • eventUrl (required): The URL of the event to update

  • summary (optional): New event title

  • description (optional): New event description

  • startDate (optional): New start date/time in ISO format

  • endDate (optional): New end date/time in ISO format

  • location (optional): New event location

Returns: Success message.

delete_event

Deletes a calendar event.

Parameters:

  • eventUrl (required): The URL of the event to delete

  • etag (required): The etag of the event (obtained from list_events)

Returns: Success message.

Example Usage

Once installed, you can ask your AI assistant:

  • "List my Fastmail calendars"

  • "Show me my calendar events for next week"

  • "Create a meeting on December 15th at 2 PM titled 'Team Sync'"

  • "Update the 'Team Sync' event to include a Zoom link in the description"

  • "Delete the event with URL [event-url]"

Security Notes

  • Never commit your Fastmail app password to version control

  • Use environment variables or secure secret management

  • App passwords are safer than your main Fastmail password

  • You can revoke app passwords at any time from Fastmail settings

License

MIT

Available Tools

6 tools
create_eventA

Create a new calendar event. PREREQUISITE: You must first call list_calendars to get the calendarUrl. Creates an event with the specified title, times, and optional description/location.

Inputs: calendarUrl (required), summary (required), startDate (required), endDate (required), +2 more.

delete_eventA
DestructiveIdempotent

PERMANENTLY DELETE an event. PREREQUISITE: You must first call list_calendars, then list_events to get both the eventUrl AND etag. WARNING: This cannot be undone. Always confirm with the user before deleting.

Inputs: eventUrl (required), etag (required).

get_event_detailsA
Read-onlyIdempotent

Get parsed details of a specific event. PREREQUISITE: You must first call list_calendars, then list_events to get the eventUrl. Returns structured event data (title, start, end, location, description) instead of raw iCalendar format.

Inputs: eventUrl (required).

list_calendarsA
Read-onlyIdempotent

STEP 1 - ALWAYS CALL THIS FIRST. Lists all calendars in the user's Fastmail account. Returns an array of calendars with displayName (human-readable name like "Work", "Personal", "Family"), url (required for other operations), and timezone. You MUST call this before list_events, create_event, update_event, or delete_event to get the calendar URL. Look at the displayName to identify which calendar the user wants (e.g., "Work" for work schedule, "Personal" for personal events).

Inputs: no named parameters.

list_eventsA
Read-onlyIdempotent

STEP 2 - Get events from a calendar. PREREQUISITE: You must first call list_calendars to get the calendarUrl. Returns events within the specified date range. Each event contains: url (needed for update/delete), etag (needed for delete), and data (iCalendar format with SUMMARY=title, DTSTART=start time, DTEND=end time, LOCATION, DESCRIPTION). Parse the iCalendar data to show event details to the user.

Inputs: calendarUrl (required), startDate (required), endDate (required).

update_eventA
Idempotent

Modify an existing event. PREREQUISITE: You must first call list_calendars, then list_events to get the eventUrl. Only include fields you want to change; omitted fields stay the same.

Inputs: eventUrl (required), summary, description, startDate, +2 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: list_calendars and list_events are for discovery, create_event and update_event for modifications, get_event_details for reading parsed data, and delete_event for removal. The prerequisites and descriptions reinforce their unique roles, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_calendars, create_event, delete_event) using snake_case throughout. This predictability makes the tool set easy to navigate and understand at a glance.

    Tool Count5/5

    With 6 tools, the server is well-scoped for calendar management, covering essential CRUD operations (create, read, update, delete) plus necessary discovery steps (list_calendars, list_events). Each tool earns its place without bloat or gaps.

    Completeness5/5

    The tool set provides complete coverage for calendar event management: discovery (list_calendars, list_events), creation (create_event), reading (get_event_details), updating (update_event), and deletion (delete_event). There are no dead ends or obvious gaps, supporting full lifecycle workflows.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to connect to CalDAV servers and manage calendars through natural language, including listing calendars and browsing, creating, updating, and deleting events and tasks (VTODOs). Supports recurring events, all-day events, due-date filtering, status changes, and pagination of long task lists.
      511 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to connect to calendar servers and manage events and tasks, including listing calendars, querying timeframes, creating, updating, completing, and deleting items through tools.
      511 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to connect to CalDAV servers and manage calendars, events, and tasks through tools for listing, creating, updating, completing, and deleting items.
      511 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to read, search, send, and organize email, manage contacts, and create or update calendar events through the Fastmail JMAP, CalDAV, and WebDAV APIs, including attachments, drafts, labels, and bulk operations.
      MIT