Fastmail Calendar MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMAIL_USERNAME | Yes | Your Fastmail email address (e.g., user@fastmail.com) | |
| FASTMAIL_APP_PASSWORD | Yes | A Fastmail app password (16 characters) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_calendarsA | 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). |
| list_eventsA | 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. |
| get_event_detailsA | 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. |
| 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. |
| update_eventA | 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. |
| delete_eventA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| schedule_meeting | Help schedule a new meeting or appointment on your calendar |
| daily_agenda | Get your agenda for today or a specific date |
| find_free_time | Find available time slots in your calendar |
| weekly_summary | Get a summary of your upcoming week's schedule |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.