Productivity · Local MCP server
Temporal Cortex Calendar MCP
18 deterministic calendar tools: contact resolution, temporal context, availability, booking.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.temporal-cortex/mcp- Version
- 0.9.1
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-03-10
- Updated
- 2026-03-10
- Publisher
- temporal-cortex (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/temporal-cortex) · how
- Listed under
- Calendar MCP servers
- Repository
- github.com/temporal-cortex/mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @temporal-cortex/cortex-mcp | 0.9.1 | stdio |
How to connect Temporal Cortex Calendar MCP
Temporal Cortex Calendar MCP runs locally from a Node.js package published to the npm registry: @temporal-cortex/cortex-mcp version 0.9.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @temporal-cortex/cortex-mcp@0.9.1. It reads these environment variables: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GOOGLE_OAUTH_CREDENTIALS, MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET (secret), TIMEZONE, WEEK_START, TENANT_ID, LOCK_TTL_SECS, OAUTH_REDIRECT_PORT, HTTP_PORT, HTTP_HOST, ALLOWED_ORIGINS, TEMPORAL_CORTEX_TELEMETRY and REDIS_URLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@temporal-cortex/cortex-mcp@0.9.1"
],
"env": {
"GOOGLE_CLIENT_ID": "<value>",
"GOOGLE_CLIENT_SECRET": "<secret>",
"GOOGLE_OAUTH_CREDENTIALS": "<value>",
"MICROSOFT_CLIENT_ID": "<value>",
"MICROSOFT_CLIENT_SECRET": "<secret>",
"TIMEZONE": "<value>",
"WEEK_START": "<value>",
"TENANT_ID": "<value>",
"LOCK_TTL_SECS": "<value>",
"OAUTH_REDIRECT_PORT": "<value>",
"HTTP_PORT": "<value>",
"HTTP_HOST": "<value>",
"ALLOWED_ORIGINS": "<value>",
"TEMPORAL_CORTEX_TELEMETRY": "<value>",
"REDIS_URLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Tempi accountRun your own Tempi scheduling account: event types, working hours, calendars and bookings. | Remote · HTTPLive check: sign-in required |
| templated.emailCreate and manage Templated email templates from any MCP client - bring your own model. | Remote & Local · HTTP, stdioLive check: sign-in required |
| TemplateFoxPDF MCP-SERVERMCP server for TemplateFox PDF generation API - Generate PDFs from templates via AI assistants. | Local · stdio |
| Tempo Api MCPTempo time-tracking for Claude - worklogs, plans, and timesheet approvals. | Local · stdio |
| TemwayVisual email & layout builder that turns AI assistants into a Temway authoring studio. | Remote · HTTPLive check: ✗ no handshake |
| Tend MCPUnofficial MCP server for Tend Dental appointment booking. Not affiliated with Tend. | Local · stdio |
| Tendem MCP serverDelegate tasks to vetted human experts - research, writing, analysis, and data work. | Remote · HTTPLive check: sign-in required |
| Teneo Book GenerationPublish-ready nonfiction books from a topic: manuscript, cover, PDF/EPUB/DOCX. Free outline to try. | Local · stdio |