Open Source · MCP Server · Agent Skills
Scheduling infrastructure of the agentic web
Resolve any person to their true availability. Atomic booking. Zero hallucinations. Built for a world where agents schedule on your behalf.
Why do AI agents keep double-booking your calendar?
Even the latest LLMs — GPT-5, Claude, Gemini — score below 50% on temporal reasoning tasks (OOLONG benchmark). Earlier models scored as low as 29% on scheduling and 13% on duration calculations (Test of Time, ICLR 2025). Most Calendar MCP servers pass these failures through because they are thin CRUD wrappers — no locking, no conflict detection, and no availability computation. Temporal Cortex solves this with atomic booking via Two-Phase Commit, deterministic RRULE expansion, and cross-provider availability merging.
<50%
LLM temporal reasoning accuracy
Even GPT-5 scores below 50% on temporal reasoning tasks. (OOLONG, Test of Time)
0
MCP servers with locking
Most Calendar MCP servers are thin CRUD wrappers — no locking, no conflict detection, no availability computation.
3+
Calendar silos per person
Your calendars are fragmented — Google for work, Outlook for enterprise, iCloud for personal. Agents inherit this blindness.
What makes Temporal Cortex different from other Calendar MCP servers?
Temporal Cortex is the only Calendar MCP server with atomic booking (Two-Phase Commit with distributed locking), deterministic RRULE expansion (Truth Engine, written in Rust), and cross-provider availability merging (Google Calendar + Outlook + CalDAV in one unified view). No other MCP server combines all three.
Atomic Booking (2PC)
Lock → verify → write → release. If any step fails, everything rolls back. Zero double-bookings, even with concurrent agents.
book_slot({
calendar_id: "primary",
title: "Team Sync",
start: "2026-02-26T14:00",
end: "2026-02-26T15:00"
})
// Lock acquired → conflict check → booked ✓Truth Engine
Deterministic RRULE expansion. Handles DST transitions, BYSETPOS, EXDATE with timezones, leap years. Not API-dependent — computed locally.
expand_rrule({
rrule: "FREQ=WEEKLY;BYDAY=MO,WE,FR",
dtstart: "2026-02-01T09:00",
count: 10
})
// 10 exact occurrences, DST-safe ✓Availability Merging
Returns "these slots are free across all calendars" — not raw events for you to figure out. Google + Outlook + iCloud in one view.
get_availability({
calendars: ["google/primary",
"outlook/work", "caldav/personal"],
date: "2026-02-27"
})
// Merged free slots across all ✓Token-efficient by default — TOON format reduces calendar data by ~40%
All data tools return results in TOON (Token-Optimized Object Notation), a structured format designed for LLM consumption. Fewer tokens per response means faster agent reasoning and lower API costs — without sacrificing readability.
How does Temporal Cortex work?
Install with npx @temporal-cortex/cortex-mcp. Authenticate with your calendar provider via OAuth. Your AI agent immediately gets 12 tools across 4 layers — temporal context, calendar operations, availability computation, and safe booking. The typical workflow follows 4 steps:
Install
npx @temporal-cortex/cortex-mcp
Authenticate
npx @temporal-cortex/cortex-mcp auth google
OAuth opens in your browser. One-time consent, credentials stored locally.
Your agent gets 12 tools across 4 layers
Temporal context, calendar operations, availability computation, and safe booking.
Agent schedules intelligently
get_temporal_context → resolve_datetime → find_free_slots → book_slot
10 seconds to first tool call. Full calendar access within 2 minutes.
How does Temporal Cortex compare?
Temporal Cortex is the only Calendar MCP server with atomic booking, RRULE expansion, multi-provider availability merging, and temporal context tools. Here's how it compares to alternatives:
| Feature | Temporal Cortex | nspady | rauf543 | MS Agent 365 |
|---|---|---|---|---|
| Atomic booking (2PC) | ✓ | ✗ | ✗ | ✗ |
| RRULE expansion | ✓ | ✗ | ✗ | ✗ |
| Multi-provider merge | ✓ | Partial | ✓ | ✗ |
| Availability computation | ✓ | ✗ | ✗ | ✗ |
| Open source | ✓ | ✓ | ✓ | ✗ |
| Temporal context (date/time math) | ✓ | ✗ | ✗ | ✗ |
Start free. Scale when you're ready.
Open source with no limits. Managed platform for teams. Pro for open scheduling.
Starter
$0
Account required
- ✓ 3 connected calendars
- ✓ 50 bookings/month
- ✓ Managed hosting
Pro
$29/mo
Open Scheduling
- ✓ Unlimited calendars
- ✓ 500 bookings/month
- ✓ Inbound booking + 2PC
Open Source
Free
Forever. No limits.
- ✓ All 12 tools
- ✓ No account required
- ✓ Your machine, your data
npx @temporal-cortex/cortex-mcpThe future is agent-to-agent scheduling
Today, AI agents use MCP tools to access calendars. Tomorrow, agents will negotiate scheduling with other agents directly. Temporal Cortex is building the infrastructure for this transition — from MCP tools to Agent Cards to the agentic web.
Today
The Tool Era
Agents use MCP tools to access calendars. You install a server and your agent gets 12 tools.
2027
The Agent Card Era
Each user gets an A2A-compliant scheduling agent. Agent Cards declare capabilities. Discovery via identity resolution.
2028+
The Agentic Web
Agent-to-agent scheduling in under 2 seconds, zero human intervention. Temporal Cortex becomes DNS for Human Time.
Give your AI agent a calendar that works
Install in 10 seconds. No account required. All 12 tools, immediately.
Questions? GitHub Issues are open.