Temporal Cortex MCP

What temporal-cortex/mcp MCP server does

temporal-cortex/mcp MCP server adds calendar scheduling capabilities to MCP-compatible AI clients. It supports Google Calendar, Microsoft Outlook, and CalDAV providers, including services such as iCloud and Fastmail when configured through CalDAV. The toolset covers calendar discovery, event listing, timezone conversion, human-readable datetime resolution, duration calculation, recurrence expansion, availability queries, and booking.

The server also supports open scheduling through Temporal Cortex profiles. Agents can resolve a person from an email, phone number, or agent ID, inspect public availability by slug, and request a booking when Platform Mode is enabled. Contact search and contact resolution can identify whether a person should be scheduled through open scheduling, email, or phone.

How it works

An agent can begin with get_temporal_context to establish the current time, timezone, and calendar metadata, then use list_calendars to discover connected calendars. list_events, find_free_slots, and get_availability provide calendar data for a selected period. The multi-calendar availability tool merges events into one busy/free view and supports privacy controls.

Temporal operations are computed rather than left to model interpretation. resolve_datetime converts expressions such as “next Tuesday at 2pm” or “in 2 hours” into absolute timestamps, while convert_timezone, adjust_timestamp, and compute_duration handle related calculations. expand_rrule turns recurrence rules into event instances, including timezone-sensitive cases.

For booking, check_availability tests a slot and book_slot uses a Two-Phase Commit process. If another booking wins the slot, the operation reports a conflict instead of silently creating a double booking. compose_proposal only formats a message; it does not send email, Slack, or SMS.

Setup and configuration

The local package requires Node.js 18 or newer, or Docker, plus at least one calendar provider. Google Calendar uses OAuth client credentials, Outlook requires an Azure AD application and MICROSOFT_CLIENT_ID, and CalDAV requires an app-specific password. The interactive setup command can guide provider authentication, timezone configuration, and MCP client setup.

Install the local server with npx -y @temporal-cortex/cortex-mcp. The documented MCP configurations use environment variables such as GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and TIMEZONE. A managed Platform option is also available through the Temporal Cortex web application; it uses connected calendars and an API key instead of requiring a local Node.js setup.

Tools and capabilities

The listed tools include:

• Discover calendars and events with list_calendars and list_events.
• Resolve identities and contacts with resolve_identity, search_contacts, and resolve_contact.
• Calculate time values with resolve_datetime, convert_timezone, adjust_timestamp, and compute_duration.
• Inspect availability with find_free_slots, get_availability, and check_availability.
• Book or propose meetings with book_slot, request_booking, and compose_proposal.
• Expand recurring schedules with expand_rrule.

Data-oriented tools default to TOON output, with JSON available through an explicit format option according to the README.

Limitations and notes

Public availability queries and booking through another person’s Temporal Link require Platform Mode. Contact searching requires contacts permission. request_booking also requires an attendee email and returns a conflict if the requested slot has already been taken, so the agent should query availability again.

The local installation still requires provider credentials and configuration. The server does not send proposal messages itself; another channel-specific MCP server or integration must deliver the text returned by compose_proposal. temporal-cortex/mcp MCP server is distributed under the MIT license, while the managed Platform is a separate hosted usage path.