Temporal Cortex Calendar MCP
Give coding agents deterministic calendar context, availability checks, and booking actions against Google or Outlook without hand-rolling OAuth flows.
Overview
Temporal Cortex Calendar MCP is a Build-phase MCP server that gives agents twelve deterministic tools for calendar context, scheduling, availability, and booking on Google or Outlook.
What is this MCP server?
- 12 deterministic calendar tools for temporal context, scheduling, availability, and booking
- stdio npm package @temporal-cortex/cortex-mcp (registry v0.5.0)
- Google Calendar via GOOGLE_CLIENT_ID/SECRET or GOOGLE_OAUTH_CREDENTIALS JSON path
- Outlook Calendar via MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET
- Optional IANA TIMEZONE override (e.g. America/New_York) for consistent agent reasoning
- 12 deterministic calendar tools documented in the registry description
- Server schema version 0.5.0 with npm package @temporal-cortex/cortex-mcp
- stdio transport with documented Google and Microsoft OAuth environment variables
What problem does it solve?
Agents hallucinate dates and cannot reliably check real availability or book meetings without a governed calendar integration.
Who is it for?
Solo builders adding meeting scheduling, standup planning, or time-boxed workflows into Claude Code or Cursor with Google or Outlook calendars already in use.
Skip if: Teams that only need a one-off reminder in notes, run fully offline calendars, or refuse to configure Google or Azure OAuth secrets.
What do I get? / Deliverables
Your agent can query live calendar state, propose slots, and execute booking flows with OAuth-backed Google or Microsoft access and optional timezone pinning.
- MCP-exposed calendar read and scheduling tool surface for your agent
- OAuth-configured Google and/or Microsoft calendar connectivity
- Timezone-aware temporal context for agent prompts and automation
Recommended MCP Servers
Journey fit
Calendar MCP is primarily an agent integration you wire during product build, even though you reuse it when scheduling user research, sales calls, and ops syncs later. integrations is the canonical shelf for stdio MCP servers that connect Claude Code or Cursor to external SaaS APIs like Google Calendar and Microsoft Graph.
How it compares
MCP calendar integration with deterministic tools, not a standalone scheduling SaaS or a generic brainstorming skill.
Common Questions / FAQ
Who is Temporal Cortex Calendar MCP for?
It is for indie developers and small teams who want coding agents to read and act on real Google or Outlook calendars through MCP instead of manual exports.
When should I use Temporal Cortex Calendar MCP?
Use it when you are building or extending an agent workflow that must know the current time context, find open slots, or book events during development or customer operations.
How do I add Temporal Cortex Calendar MCP to my agent?
Install @temporal-cortex/cortex-mcp, register the stdio server in your MCP client, and set Google or Microsoft OAuth variables plus optional TIMEZONE before starting the process.