Temporal Mcp
Give long-running coding agents wall-clock awareness—elapsed time between turns and day-boundary detection—so sessions respect real-world pacing.
Overview
temporal-mcp is a MCP server for the Build phase that exposes two tools for wall-clock elapsed time between turns and day rollover detection for LLM agents.
What is this MCP server?
- Exactly two MCP tools: elapsed-time-between-turns and day rollover detection
- Hosted streamable-http remote at temporal-mcp.dev plus PyPI stdio package temporal-mcp v0.2.0
- Bearer Authorization with user-chosen opaque token (SHA-256 stored server-side)
- Helps agents notice multi-hour gaps and calendar day changes across threads
- Lightweight dependency for session continuity without external calendar APIs
- 2 MCP tools: elapsed-time-between-turns and day rollover detection
- Server version 0.2.0 with HTTP remote and PyPI stdio package
- Authorization uses client-chosen opaque bearer token (SHA-256 hashed for storage)
Community signal: 2 GitHub stars.
What problem does it solve?
Your agent treats a conversation as timeless and cannot tell how long you were away or when a new day started.
Who is it for?
Builders adding session-time awareness to agents that run across hours or days without building a custom clock service.
Skip if: Production cron orchestration, team calendar sync, or application-level metrics monitoring in operate phase.
What do I get? / Deliverables
After registration, the agent can query elapsed durations and day changes to pace reminders, summaries, and time-sensitive plans accurately.
- Elapsed-time-between-turns measurements for the agent
- Day rollover detection across session boundaries
- Private timeline keyed by your bearer token on hosted remote
Recommended MCP Servers
Journey fit
Temporal context is agent infrastructure added during build when you wire MCP servers into Claude Code, Cursor, or custom agents. Agent-tooling hosts MCP utilities that change how the agent reasons about sessions, not your app’s production monitoring stack.
How it compares
Minimal wall-clock MCP for agents, not a workflow engine like Temporal.io or full APM monitoring.
Common Questions / FAQ
Who is Temporal Mcp for?
Developers wiring MCP into coding agents who need simple elapsed-time and day-change signals across long or intermittent chats.
When should I use Temporal Mcp?
Use it when agent workflows reference deadlines, daily habits, or multi-session continuity and wall-clock gaps matter.
How do I add Temporal Mcp to my agent?
Choose the remote URL https://Temporal Mcp.dev/mcp with Authorization Bearer plus your private token, or install the PyPI Temporal Mcp stdio package v0.2.0 in your MCP config.