Temporal Cortex Calendar MCP

Name: Temporal Cortex Calendar MCP
Author: temporal-cortex

by temporal-cortexversion 0.9.1i★ –iRuns on your computer

Registry nameio.github.temporal-cortex/mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work
You need to fill in: GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: 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

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "temporal-cortex": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_OAUTH_CREDENTIALS": "your-value",
        "MICROSOFT_CLIENT_ID": "your-value",
        "MICROSOFT_CLIENT_SECRET": "your-value",
        "TIMEZONE": "your-value",
        "WEEK_START": "your-value",
        "TENANT_ID": "your-value",
        "LOCK_TTL_SECS": "your-value",
        "OAUTH_REDIRECT_PORT": "your-value",
        "HTTP_PORT": "your-value",
        "HTTP_HOST": "your-value",
        "ALLOWED_ORIGINS": "your-value",
        "TEMPORAL_CORTEX_TELEMETRY": "your-value",
        "REDIS_URLS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add temporal-cortex --env GOOGLE_CLIENT_ID=your-value --env GOOGLE_CLIENT_SECRET=your-value --env GOOGLE_OAUTH_CREDENTIALS=your-value --env MICROSOFT_CLIENT_ID=your-value --env MICROSOFT_CLIENT_SECRET=your-value --env TIMEZONE=your-value --env WEEK_START=your-value --env TENANT_ID=your-value --env LOCK_TTL_SECS=your-value --env OAUTH_REDIRECT_PORT=your-value --env HTTP_PORT=your-value --env HTTP_HOST=your-value --env ALLOWED_ORIGINS=your-value --env TEMPORAL_CORTEX_TELEMETRY=your-value --env REDIS_URLS=your-value -- npx -y @temporal-cortex/cortex-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "temporal-cortex": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_OAUTH_CREDENTIALS": "your-value",
        "MICROSOFT_CLIENT_ID": "your-value",
        "MICROSOFT_CLIENT_SECRET": "your-value",
        "TIMEZONE": "your-value",
        "WEEK_START": "your-value",
        "TENANT_ID": "your-value",
        "LOCK_TTL_SECS": "your-value",
        "OAUTH_REDIRECT_PORT": "your-value",
        "HTTP_PORT": "your-value",
        "HTTP_HOST": "your-value",
        "ALLOWED_ORIGINS": "your-value",
        "TEMPORAL_CORTEX_TELEMETRY": "your-value",
        "REDIS_URLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "temporal-cortex": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your-value",
        "GOOGLE_CLIENT_SECRET": "your-value",
        "GOOGLE_OAUTH_CREDENTIALS": "your-value",
        "MICROSOFT_CLIENT_ID": "your-value",
        "MICROSOFT_CLIENT_SECRET": "your-value",
        "TIMEZONE": "your-value",
        "WEEK_START": "your-value",
        "TENANT_ID": "your-value",
        "LOCK_TTL_SECS": "your-value",
        "OAUTH_REDIRECT_PORT": "your-value",
        "HTTP_PORT": "your-value",
        "HTTP_HOST": "your-value",
        "ALLOWED_ORIGINS": "your-value",
        "TEMPORAL_CORTEX_TELEMETRY": "your-value",
        "REDIS_URLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

GOOGLE_CLIENT_ID env
Google OAuth Client ID (required for Google Calendar)
GOOGLE_CLIENT_SECRET secret env
Google OAuth Client Secret (required if using Google Calendar)
GOOGLE_OAUTH_CREDENTIALS env
Path to Google OAuth JSON credentials file (alternative to CLIENT_ID + SECRET)
MICROSOFT_CLIENT_ID env
Azure AD app ID (required for Outlook Calendar)
MICROSOFT_CLIENT_SECRET secret env
Azure AD client secret (required for Outlook Calendar)
TIMEZONE env
IANA timezone override (e.g., America/New_York). Overrides stored config and OS detection.
WEEK_START env
Week start day: 'monday' (default, ISO 8601) or 'sunday'. Overrides stored config.
TENANT_ID env
UUID for tenant isolation (auto-generated if not set)
LOCK_TTL_SECS env
Lock time-to-live in seconds for booking safety
OAUTH_REDIRECT_PORT env
Port for the local OAuth callback server
HTTP_PORT env
Port for HTTP transport. When set, enables streamable HTTP mode instead of stdio.
HTTP_HOST env
Bind address for HTTP transport (default: 127.0.0.1)
ALLOWED_ORIGINS env
Comma-separated allowed Origin headers for HTTP mode. Cross-origin requests rejected if unset.
TEMPORAL_CORTEX_TELEMETRY env
Override telemetry consent: 'off' to disable, 'on' to enable anonymous usage analytics.
REDIS_URLS env
Comma-separated Redis URLs for distributed locking within Platform Mode. Optional.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account temporal-cortex, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2166 servers in this category
Published to the registry more recently than 4% of the other 2166 servers in this category
Basic checks equal to or better than 100% of the other 2166 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Temporal Cortex Calendar MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.1) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 5 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 3 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Temporal Cortex MCP

v0.9.1 · March 2026 · Changelog · Website: temporal-cortex.com

Give any AI agent autonomous scheduling capabilities. Temporal Cortex is open scheduling infrastructure that lets any AI agent schedule reliably — whether the other person has an AI agent or not, uses Google Calendar or Outlook, or responds instantly or days later. 18 tools across 5 layers handle contact resolution, temporal reasoning, cross-provider availability, and atomic booking. Accessible via MCP, A2A, REST, and browser. Powered by Truth Engine. Install: npx @temporal-cortex/cortex-mcp.

Two ways to use Temporal Cortex

For individuals

Connect your calendars. Your AI agent handles the rest — checking availability, resolving time zones, and booking meetings without double-booking. Works with Claude Desktop, Cursor, OpenClaw, Manus, and any MCP-compatible AI client.

npx @temporal-cortex/cortex-mcp setup

The setup wizard walks you through provider authentication, timezone configuration, and MCP client setup interactively. You'll be scheduling in under a minute.

Or use the managed Platform — no Node.js required. Sign up at app.temporal-cortex.com, connect your calendars via OAuth, and add a single MCP config with your API key.

For developers

Add scheduling to your AI agent or product. 18 tools across 5 layers, 4 protocols (MCP, A2A, REST, Browser), atomic booking with Two-Phase Commit, and deterministic temporal computation powered by Truth Engine.

Local MCP server: npx @temporal-cortex/cortex-mcp — full tool suite, zero infrastructure
Platform REST API: app.temporal-cortex.com — managed hosting, API keys, usage dashboard, Open Scheduling network
Framework integrations: LangGraph, CrewAI, OpenAI Agents SDK
REST API reference: temporal-cortex.com/docs/rest-api

Why do AI agents fail at calendar tasks?

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). Ask "Schedule for next Tuesday at 2pm" and it picks the wrong Tuesday. Ask "Am I free at 3pm?" and it checks the wrong timezone. Then it double-books your calendar.

Most calendar tools for AI agents are thin CRUD wrappers that pass these failures through to a single calendar provider — no temporal awareness, no conflict detection, no safety net.

What makes Temporal Cortex different?

Temporal awareness — Agents call get_temporal_context to know the actual time and timezone. resolve_datetime turns "next Tuesday at 2pm" into a precise RFC 3339 timestamp. No hallucination.
Atomic booking — Lock the time slot, verify no conflicts exist, then write. Two agents booking the same 2pm slot? Exactly one succeeds. The other gets a clear error. No double-bookings.
Computed availability — Merges free/busy data across multiple calendars into a single unified view. The AI sees actual availability, not a raw dump of events to misinterpret.
Deterministic RRULE expansion — Handles DST transitions, BYSETPOS=-1 (last weekday of month), EXDATE with timezones, leap year recurrences, and INTERVAL>1 with BYDAY. Powered by Truth Engine, not LLM inference.
Token-efficient output — TOON format compresses calendar data by ~40% fewer tokens than standard JSON, reducing costs and context window usage. TOON is the default output format for all data tools (list_calendars, list_events, find_free_slots, expand_rrule, get_availability). JSON is available via explicit format: "json".

What do I need to run Temporal Cortex?

Node.js 18+ (for npx to download and run the binary) or Docker
At least one calendar provider:
Google Calendar — requires Google OAuth credentials
Microsoft Outlook — requires Azure AD app registration (MICROSOFT_CLIENT_ID)
CalDAV (iCloud, Fastmail, etc.) — requires an app-specific password

How do I install Temporal Cortex?

The fastest way to get started:

npx @temporal-cortex/cortex-mcp setup

The cortex-mcp setup wizard walks you through provider authentication, timezone configuration, and MCP client setup interactively. See the First Run Guide for a detailed walkthrough.

Or set up manually in 3 steps:

Install prerequisites — Node.js 18+ (or Docker) and at least one calendar provider (Google Calendar, Microsoft Outlook, or CalDAV).
Add the MCP configuration to your AI client's config file (see client-specific examples below).
Run the auth flow — npx @temporal-cortex/cortex-mcp auth google (or outlook / caldav). This authenticates and configures timezone, week start, and telemetry preferences.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

"mcpServers": { "temporal-cortex": { "command": "npx", "args": ["-y", "@temporal-cortex/cortex-mcp"], "env": { "GOOGLE_CLIENT_ID": "your-client-id.apps.googleusercontent.com", "GOOGLE_CLIENT_SECRET": "your-client-secret", "TIMEZONE": "America/New_York" } } } }

Cursor

Add to Cursor's MCP settings (~/.cursor/mcp.json):

Windsurf

Add to Windsurf's MCP config (~/.codeium/windsurf/mcp_config.json):

Docker

docker run --rm -i \

-e GOOGLE_CLIENT_ID="your-client-id.apps.googleusercontent.com" \ -e GOOGLE_CLIENT_SECRET="your-client-secret" \ -e TIMEZONE="America/New_York" \ -v ~/.config/temporal-cortex:/root/.config/temporal-cortex \ cortex-mcp

Build the image first: docker build -t cortex-mcp . (or build directly from the repo: docker build -t cortex-mcp https://github.com/temporal-cortex/mcp.git).

Need help with provider credentials? See the setup guides: Google Calendar, Microsoft Outlook, CalDAV (iCloud/Fastmail). For a complete reference of all environment variables and configuration options, see the Configuration Guide.

How do I verify the installation?

SHA256 checksums are published with every GitHub Release and embedded in the npm package as checksums.json for automatic postinstall verification. The postinstall script downloads the platform-specific binary and compares its SHA256 hash against the expected checksum in checksums.json. On mismatch, installation fails with an error — the binary is not installed and the error message includes both the expected and actual hashes.

Verify manually:

# Download the published checksums

curl -sL https://github.com/temporal-cortex/mcp/releases/download/mcp-v0.9.1/SHA256SUMS.txt

Compare against your installed binary

sha256sum "$(dirname "$(which cortex-mcp)")/../cortex-mcp" 2>/dev/null || \ shasum -a 256 "$(npm root -g)/@temporal-cortex/cortex-mcp/bin/cortex-mcp" 2>/dev/null

Build provenance: Binaries are cross-compiled from Rust source in GitHub Actions across 5 platforms (darwin-arm64, darwin-x64, linux-x64, linux-arm64, win32-x64). The computation layer is open source at temporal-cortex/core.

Docker containment: For maximum isolation, run the MCP server in a container:

docker build -t cortex-mcp https://github.com/temporal-cortex/mcp.git

docker run --rm -i -v ~/.config/temporal-cortex:/root/.config/temporal-cortex cortex-mcp

No Node.js on the host, no direct filesystem access beyond the mounted config directory.

How do I authenticate with calendar providers?

The easiest path is npx @temporal-cortex/cortex-mcp setup, which handles authentication, configuration, and MCP client setup in one guided flow. For individual provider auth, run the commands below:

# Google Calendar (default)

npx @temporal-cortex/cortex-mcp auth google

Microsoft Outlook

npx @temporal-cortex/cortex-mcp auth outlook

CalDAV (iCloud, Fastmail, or custom server)

npx @temporal-cortex/cortex-mcp auth caldav

Docker (interactive auth — needs terminal + browser)

docker run --rm -it \ -e GOOGLE_CLIENT_ID="your-id" -e GOOGLE_CLIENT_SECRET="your-secret" \ -p 8085:8085 \ -v ~/.config/temporal-cortex:/root/.config/temporal-cortex \ cortex-mcp auth google

Each auth flow saves credentials to ~/.config/temporal-cortex/credentials.json and registers the provider in ~/.config/temporal-cortex/config.json. You can connect multiple providers — the server discovers all configured providers on startup and merges their calendars into a unified view.

During auth, the server guides you through interactive setup:

Timezone — auto-detects your system timezone and opens a fuzzy-search picker with al

Only the beginning is shown; read the rest in the repo

Temporal Cortex Calendar MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Temporal Cortex MCP

Two ways to use Temporal Cortex

For individuals

For developers

Why do AI agents fail at calendar tasks?

What makes Temporal Cortex different?

What do I need to run Temporal Cortex?

How do I install Temporal Cortex?

Claude Desktop

Cursor

Windsurf

Docker

How do I verify the installation?

Compare against your installed binary

How do I authenticate with calendar providers?

Microsoft Outlook

CalDAV (iCloud, Fastmail, or custom server)

Docker (interactive auth — needs terminal + browser)