ToolsMCP
Temporal Cortex Calendar MCP
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- temporal-cortex (GitHub)
- Prerequisites
- Install @temporal-cortex/cortex-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.9.1 · updated
- Official links
Publisher’s description
18 deterministic calendar tools: contact resolution, temporal context, availability, booking
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.9.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- temporal-cortex (GitHub)
- Version observed
- 0.9.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.temporal-cortex%2Fmcp/versions/0.9.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Manage calendar events from an assistant | Publisher description mentions “calendar”, “availability”. | No connection check or task run. Capability is as described by the publisher. | Rule calendar-events matched: “calendar”, “availability”. Rule calendar-events. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@temporal-cortex/cortex-mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.temporal-cortex/mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.