mcpbeat Sign in

Temporal Cortex Calendar MCP Server

by temporal-cortex Your server? Claim it
local only

Temporal Cortex Calendar MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 323 installs a week from npm. Last commit 21 Apr 2026.

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

Installs per day peak 131 · avg 18 · +602% w/w
a month agotoday
323
Installs / week
npm · @temporal-cortex/cortex-mcp
13
Stars
0 open issues
21 Apr 2026
Last commit
no releases in 90 days
MIT
License
Dockerfile

What the code does

We read the source, 3 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs a command on install [пакет] package.json:1
postinstall: node scripts/postinstall.js
File ships in the package but is absent from the source [пакет] bin/run.js:1
этот файл ставится пользователю, но в репозитории его нет
Runs an external command [пакет] bin/run.js:67
  execFileSync(binPath, process.argv.slice(2), {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add mcp -- npx -y @temporal-cortex/cortex-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ]
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
command = "npx"
args = ["-y", "@temporal-cortex/cortex-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ]
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@temporal-cortex/cortex-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: GOOGLE_CLIENT_ID (Google OAuth Client ID (required for Google Calendar)), GOOGLE_CLIENT_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 (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 for distributed locking within Platform Mode. Optional).

Alternatives to Temporal Cortex Calendar MCP

same job, measured the same way
Temporal Cortex Calendar MCP
by billylui

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

local only
Availability
by theluckystrike

Read .ics calendar exports: free-busy, availability windows, double bookings, conflicts.

local only
Tgms
by zxf-work

Bi-temporal graph store with 15 verified temporal operators as typed, deterministic MCP tools.

211 installs/wk local only
Reservations
by tehprof-booking

Remote MCP for TehProf Booking: browse resources & availability, create & cancel reservations.

8 tools answering
contextweaver
by dgenio

MCP gateway: bounded tool shortlists + artifact-backed result firewall. Deterministic, no model.

144 installs/wk local only
NuVista Haven MCP Server
by cswarey16

AI front desk for NuVista Haven vacation rentals: live availability, rates, booking links.

5 tools answering
RentalCal
by rentalcal

Find direct-booking vacation rentals, check availability, and get stay quotes.

4 tools answering
MetaGO Algorithms
by metago-ai

927 deterministic algorithms as 57 MCP tools: coupling, value, distance, correlation, reduction.

400 installs/wk local only

Temporal Cortex Calendar MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Temporal Cortex Calendar MCP?
Temporal Cortex Calendar MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @temporal-cortex/cortex-mcp was installed 323 times last week.
How do I connect Temporal Cortex Calendar MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @temporal-cortex/cortex-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Temporal Cortex Calendar MCP?
The npm package @temporal-cortex/cortex-mcp was installed 323 times in the last week. Week over week that is +602%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Temporal Cortex Calendar MCP open source?
Yes — it is published under the MIT licence, written in Dockerfile and 13 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.