Temporal Cortex Calendar MCP

io.github.billyluiPublished by GitHub account billyluiv0.5.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

A local MCP server exposing 12 deterministic calendar tools for temporal context, scheduling, availability, and booking.

What you can do
Temporal Cortex Calendar MCP runs locally and gives an assistant twelve deterministic calendar tools covering temporal context, scheduling, availability lookup, and booking. It can connect to Google Calendar and Outlook Calendar through OAuth credentials, and supports an optional HTTP transport mode in addition to stdio. A Platform Mode with distributed locking via Redis is available for multi-instance setups, and booking safety is governed by a lock time-to-live setting.
When to use it
Use it when an assistant needs to reason about time and manage real calendar events, such as checking availability, proposing or booking slots, and answering scheduling questions. It suits desktop users who want calendar access tied to their own Google or Outlook accounts rather than a hosted service.
Requirements
Runs as a local process, installed from the npm package, so Node.js is required. Google Calendar needs GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET, or a credentials file path via GOOGLE_OAUTH_CREDENTIALS; Outlook Calendar needs MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET. Optional settings include HTTP_PORT and HTTP_HOST for HTTP mode, ALLOWED_ORIGINS for cross-origin requests, REDIS_URLS for Platform Mode, OAUTH_REDIRECT_PORT, TIMEZONE, WEEK_START, TENANT_ID, LOCK_TTL_SECS, and…
Before you install
It handles OAuth client secrets (GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_SECRET) and calendar data, so store credentials carefully. Booking tools can create or change events on connected calendars, and Platform Mode with REDIS_URLS adds distributed locking that affects concurrent bookings. Anonymous usage analytics are controlled by TEMPORAL_CORTEX_TELEMETRY; set it to off to disable. HTTP mode should be bound to localhost and ALLOWED_ORIGINS set, since cross-origin requests are rejected when…

Installation

In SourceWeft

  1. Open Temporal Cortex Calendar MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.5.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.