Temporal Cortex Calendar MCP

What this does

Temporal Cortex Calendar MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

GOOGLE_CLIENT_ID
GOOGLE_CLIENT_SECRET
GOOGLE_OAUTH_CREDENTIALS
MICROSOFT_CLIENT_ID
MICROSOFT_CLIENT_SECRET
TIMEZONE
WEEK_START
TENANT_ID
LOCK_TTL_SECS
OAUTH_REDIRECT_PORT
HTTP_PORT
HTTP_HOST
ALLOWED_ORIGINS
TEMPORAL_CORTEX_TELEMETRY
REDIS_URLS

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Temporal Cortex Calendar MCP?

Run the Claude Code command in the install section to add Temporal Cortex Calendar MCP to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Temporal Cortex Calendar MCP?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Temporal Cortex Calendar MCP as well.

Does Temporal Cortex Calendar MCP need an API key?

Yes. Before it can run, set these environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_OAUTH_CREDENTIALS, MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET, TIMEZONE, WEEK_START, TENANT_ID, LOCK_TTL_SECS, OAUTH_REDIRECT_PORT, HTTP_PORT, HTTP_HOST, ALLOWED_ORIGINS, TEMPORAL_CORTEX_TELEMETRY, REDIS_URLS. They go in the env block of your MCP config.