Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
Connect Remote server
claude mcp add --transport http temporal-mcp https://temporal-mcp.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"temporal-mcp": {
"url": "https://temporal-mcp.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"temporal-mcp": {
"type": "http",
"url": "https://temporal-mcp.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://temporal-mcp.dev/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 2 found in our last check
temporal_tickAdvance the temporal clock for a thread and return a snapshot (now / prev / gap / day_rollover / fresh_thread). Call once per user turn. Pass a stable `thread_key` (e.g. the conversation ID) so gap deltas remain meaningful across page reloads.
temporal_peekRead the current temporal snapshot for a thread WITHOUT advancing state. Use this when you want the gap delta but the call is not the canonical per-turn event.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer token. Pick any opaque string (UUID, passphrase, etc.) — we SHA-256 hash it for storage and never see the original. The token is your private key for your timeline. Example: 'Bearer 8c7d4b8a-...' |
Details
| Endpoint | https://temporal-mcp.dev/mcp (Streamable HTTP) |
| Package | [email protected] (PYPI, stdio) |
| First published | 13 May 2026 |
| Last updated | 13 May 2026 |
| Registry name | io.github.MirrorEthic/temporal-mcp |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
