Temporal Cortex Calendar MCP

Registre officiel Productivité

12 deterministic calendar tools — temporal context, scheduling, availability, and booking

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @temporal-cortex/cortex-mcp
Claude Code
claude mcp add temporal-cortex-calendar-mcp -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -e 'GOOGLE_OAUTH_CREDENTIALS=<GOOGLE_OAUTH_CREDENTIALS>' -e 'MICROSOFT_CLIENT_ID=<MICROSOFT_CLIENT_ID>' -e 'MICROSOFT_CLIENT_SECRET=<your microsoft_client_secret>' -e 'TIMEZONE=<TIMEZONE>' -e 'WEEK_START=monday' -e 'TENANT_ID=<TENANT_ID>' -e 'LOCK_TTL_SECS=30' -e 'OAUTH_REDIRECT_PORT=8085' -e 'HTTP_PORT=<HTTP_PORT>' -e 'HTTP_HOST=127.0.0.1' -e 'ALLOWED_ORIGINS=<ALLOWED_ORIGINS>' -e 'TEMPORAL_CORTEX_TELEMETRY=<TEMPORAL_CORTEX_TELEMETRY>' -e 'REDIS_URLS=<REDIS_URLS>' -- npx -y @temporal-cortex/cortex-mcp@0.5.0
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "temporal-cortex-calendar-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@temporal-cortex/cortex-mcp@0.5.0"
            ],
            "env": {
                "GOOGLE_CLIENT_ID": "<GOOGLE_CLIENT_ID>",
                "GOOGLE_CLIENT_SECRET": "<your google_client_secret>",
                "GOOGLE_OAUTH_CREDENTIALS": "<GOOGLE_OAUTH_CREDENTIALS>",
                "MICROSOFT_CLIENT_ID": "<MICROSOFT_CLIENT_ID>",
                "MICROSOFT_CLIENT_SECRET": "<your microsoft_client_secret>",
                "TIMEZONE": "<TIMEZONE>",
                "WEEK_START": "monday",
                "TENANT_ID": "<TENANT_ID>",
                "LOCK_TTL_SECS": "30",
                "OAUTH_REDIRECT_PORT": "8085",
                "HTTP_PORT": "<HTTP_PORT>",
                "HTTP_HOST": "127.0.0.1",
                "ALLOWED_ORIGINS": "<ALLOWED_ORIGINS>",
                "TEMPORAL_CORTEX_TELEMETRY": "<TEMPORAL_CORTEX_TELEMETRY>",
                "REDIS_URLS": "<REDIS_URLS>"
            }
        }
    }
}

Variables d'environnement

  • GOOGLE_CLIENT_ID Google OAuth Client ID (required for Google Calendar)
  • GOOGLE_CLIENT_SECRET secret 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_SECRET secret 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. When set, activates Platform Mode with distributed locking.

Questions fréquentes

Qu'est-ce que Temporal Cortex Calendar MCP ?

12 deterministic calendar tools — temporal context, scheduling, availability, and booking

Comment installer Temporal Cortex Calendar MCP ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add temporal-cortex-calendar-mcp -e 'GOOGLE_CLIENT_ID=<GOOGLE_CLIENT_ID>' -e 'GOOGLE_CLIENT_SECRET=<your google_client_secret>' -e 'GOOGLE_OAUTH_CREDENTIALS=<GOOGLE_OAUTH_CREDENTIALS>' -e 'MICROSOFT_CLIENT_ID=<MICROSOFT_CLIENT_ID>' -e 'MICROSOFT_CLIENT_SECRET=<your microsoft_client_secret>' -e 'TIMEZONE=<TIMEZONE>' -e 'WEEK_START=monday' -e 'TENANT_ID=<TENANT_ID>' -e 'LOCK_TTL_SECS=30' -e 'OAUTH_REDIRECT_PORT=8085' -e 'HTTP_PORT=<HTTP_PORT>' -e 'HTTP_HOST=127.0.0.1' -e 'ALLOWED_ORIGINS=<ALLOWED_ORIGINS>' -e 'TEMPORAL_CORTEX_TELEMETRY=<TEMPORAL_CORTEX_TELEMETRY>' -e 'REDIS_URLS=<REDIS_URLS>' -- npx -y @temporal-cortex/cortex-mcp@0.5.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Temporal Cortex Calendar MCP ?

Oui. Il attend GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET, à renseigner dans sa configuration.

Temporal Cortex Calendar MCP est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Temporal Cortex Calendar MCP ?

Il est publié par billylui. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.