Log inSubmit server
Temporal Cortex MCP logo

Temporal Cortex MCP

by temporal-cortex

Calendar MCP server for timezone-aware scheduling, cross-calendar availability, recurrence handling, and conflict-safe booking.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Temporal Cortex MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "temporal-cortex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "MICROSOFT_CLIENT_ID": "YOUR_VALUE_HERE",
        "TIMEZONE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 18 tools correctly (29d ago).

Overview

temporal-cortex/mcp MCP server gives AI agents tools for calendar discovery, temporal reasoning, availability checks, and booking. It connects to Google Calendar, Microsoft Outlook, and CalDAV, then combines calendar data into free/busy views and applies deterministic datetime and recurrence calculations. Two-Phase Commit booking helps prevent double-booking when multiple agents compete for the same slot. Reach for it when an agent must schedule meetings across calendars rather than only create or list events.

Use cases

  • Find open meeting times across Google Calendar and Outlook
  • Resolve natural-language dates before creating bookings
  • Book slots with conflict detection between competing agents
  • Expand recurring calendar rules into concrete events
  • Compose timezone-aware scheduling proposals

Key features

  • Cross-provider calendar availability
  • Deterministic timezone and datetime resolution
  • RRULE recurrence expansion
  • Two-Phase Commit booking
  • Temporal Link identity and public scheduling
  • TOON or JSON calendar output

Tools18

What Temporal Cortex MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

17/18 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · @temporal-cortex/cortex-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars13Stargazers on the source repository.
npm downloads926Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed18Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Temporal Cortex MCP works

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.

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Temporal Cortex MCP

Install and run the package with `npx -y @temporal-cortex/cortex-mcp`. The repository also documents an interactive `setup` command.

Yes. The README provides a Claude Desktop MCP configuration using `npx` and `@temporal-cortex/cortex-mcp`.

It supports Google Calendar, Microsoft Outlook, and CalDAV providers, including CalDAV services such as iCloud and Fastmail.

Yes. `book_slot` uses Two-Phase Commit, and competing bookings receive a conflict result when the slot is no longer available.

No. `compose_proposal` formats a proposal for email, Slack, or SMS, but another channel integration must send it.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTemporal Cortex MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/temporal-cortex-mcp?style=directory)](https://allmcps.com/mcp/temporal-cortex-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/temporal-cortex-mcp"><img src="https://allmcps.com/api/badge/temporal-cortex-mcp?style=directory" alt="Temporal Cortex MCP on AllMCPs" /></a>