Temporal Cortex Calendar MCP MCP Server

What the Temporal Cortex Calendar MCP MCP server does

How models use it and what it is built for.

18 deterministic calendar tools: contact resolution, temporal context, availability, booking

Connect to Temporal Cortex Calendar MCP

Hosted endpoint — paste into any MCP client.

Environment variables

Configuration this server reads at startup.

• GOOGLE_CLIENT_ID

  Google OAuth Client ID (required for Google Calendar)

• GOOGLE_CLIENT_SECRETSecret

  Google OAuth Client Secret (required if using Google Calendar)

• GOOGLE_OAUTH_CREDENTIALS

  Path to Google OAuth JSON credentials file (alternative to CLIENT_ID + SECRET)

• MICROSOFT_CLIENT_ID

  Azure AD app ID (required for Outlook Calendar)

• MICROSOFT_CLIENT_SECRETSecret

  Azure AD client secret (required for Outlook Calendar)

• TIMEZONE

  IANA timezone override (e.g., America/New_York). Overrides stored config and OS detection.

• WEEK_START

  Week start day: 'monday' (default, ISO 8601) or 'sunday'. Overrides stored config.

• TENANT_ID

  UUID for tenant isolation (auto-generated if not set)

• LOCK_TTL_SECS

  Lock time-to-live in seconds for booking safety

• OAUTH_REDIRECT_PORT

  Port for the local OAuth callback server

• HTTP_PORT

  Port for HTTP transport. When set, enables streamable HTTP mode instead of stdio.

• HTTP_HOST

  Bind address for HTTP transport (default: 127.0.0.1)

• ALLOWED_ORIGINS

  Comma-separated allowed Origin headers for HTTP mode. Cross-origin requests rejected if unset.

• TEMPORAL_CORTEX_TELEMETRY

  Override telemetry consent: 'off' to disable, 'on' to enable anonymous usage analytics.

• REDIS_URLS

  Comma-separated Redis URLs for distributed locking within Platform Mode. Optional.

Resources

Where to find authoritative docs and source for Temporal Cortex Calendar MCP.

• Source repository