MCP Servers
temporal-cortex/mcp
Calendar MCP server with atomic booking, conflict prevention, deterministic RRULE expansion, and TOON token compression for AI agents
Our verdict
We have not reviewed temporal-cortex/mcp yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About temporal-cortex/mcp
This is a Calendar MCP server for AI agents. It provides atomic booking, conflict prevention, deterministic RRULE expansion, and TOON token compression. The server is deployed using Docker.
Best for
Developers building AI agents that need reliable calendar management
Use cases
- Integrating calendar booking into AI agents
- Scheduling meetings with automatic conflict checks
- Handling recurrent events with deterministic expansion
Notes
9 stars on GitHub. Last updated 2026-04-21. Licensed MIT.
Pros
- Atomic booking ensures all-or-nothing consistency
- Conflict prevention avoids double-booking
- Deterministic RRULE expansion eliminates ambiguity in recurring events
Cons
- Low star count indicates limited community adoption
- Dockerfile deployment may require containerization knowledge
- Scope may be narrow for general calendar use cases
Key facts
What we have checked
- Days since the last commit
- 66
- GitHub forks
- 2
- GitHub stars
- 13
- Open issues
- 0
- Releases in the last 90 days
- 0
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
npx @temporal-cortex/cortex-mcp setupTools exposed
resolve_identitysearch_contactsresolve_contactget_temporal_contextresolve_datetimeconvert_timezonecompute_durationadjust_timestamplist_calendarslist_eventsfind_free_slotsexpand_rrulecheck_availabilityget_availabilityquery_public_availabilitybook_slotrequest_bookingcompose_proposalGOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET
Clients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, ChatGPT
Install
Add temporal-cortex/mcp to your client
Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.
Claude Code
Config checkedRun in your terminal (runs on your computer)
claude mcp add --transport stdio temporal-cortex-mcp -- npx -y @temporal-cortex/cortex-mcp@0.9.1Claude Desktop
Config checkedAdd to claude_desktop_config.json (runs on your computer)
{
"mcpServers": {
"temporal-cortex-mcp": {
"command": "npx",
"args": [
"-y",
"@temporal-cortex/cortex-mcp@0.9.1"
]
}
}
}Cursor
Config checkedAdd to .cursor/mcp.json (runs on your computer)
{
"mcpServers": {
"temporal-cortex-mcp": {
"command": "npx",
"args": [
"-y",
"@temporal-cortex/cortex-mcp@0.9.1"
]
}
}
}VS Code
Config checkedAdd to .vscode/mcp.json (runs on your computer)
{
"servers": {
"temporal-cortex-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@temporal-cortex/cortex-mcp@0.9.1"
]
}
}
}Codex
Config checkedAdd to ~/.codex/config.toml (runs on your computer)
[mcp_servers.temporal-cortex-mcp]
command = "npx"
args = ["-y", "@temporal-cortex/cortex-mcp@0.9.1"]- ChatGPT: ChatGPT connects only to remote servers that need no API key.
Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.
Works with
What temporal-cortex/mcp connects to
5 clients, each with how we know and when we checked.
| Works with | Type | How we know | Checked |
|---|---|---|---|
| Claude Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.9.1Config checked | Claude Code docs |
| Claude Desktop | Client | Install recipe matches the client's documented formatRuns locally, version 0.9.1Config checked | Claude Desktop docs |
| Cursor | Client | Install recipe matches the client's documented formatRuns locally, version 0.9.1Config checked | Cursor docs |
| VS Code | Client | Install recipe matches the client's documented formatRuns locally, version 0.9.1Config checked | VS Code docs |
| Codex | Client | Install recipe matches the client's documented formatRuns locally, version 0.9.1Config checked | Codex docs |
Stars and usage
How temporal-cortex/mcp is growing
13 to 13
Health and security
Is temporal-cortex/mcp looked after, and what do its setup files show
Health score
52 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 26.8 of 30 | Last push 66 days ago |
| Releases | 0 of 15 | 0 releases in 90 days |
| Issue replies | Not counted | The latest check has no issue response reading (fewer than 3 measured issues, or issues switched off) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | 0 of 20 | Community server |
Security check static checks
100 out of 100
- Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.