Temporal Cortex Calendar MCP

Name: Temporal Cortex Calendar MCP
Author: temporal-cortex

作者：temporal-cortex版本 0.9.1i★ –i在你的电脑上运行

注册名称io.github.temporal-cortex/mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公
你需要填写：GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： 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

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 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"
      }
    }
  }
}

在终端中运行这条命令

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

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "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"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

GOOGLE_CLIENT_ID env
Google OAuth Client ID (required for Google Calendar)
GOOGLE_CLIENT_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 机密 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.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 temporal-cortex 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 2173 个服务器的 0%
发布到注册中心的时间比此分类中其他 2173 个服务器的 4% 更新
基础检查结果等于或优于此分类中其他 2173 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Temporal Cortex Calendar MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.9.1）于8个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

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

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT6天前更新

安装

MCP Server for Excel

作者：sbroenne

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

在你的电脑上运行★ 847MIT3天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读