temporal-mcp
Server Details
Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- MirrorEthic/temporal-mcp
- GitHub Stars
- 2
- Server Listing
- temporal-mcp
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 2 of 2 tools scored. Lowest: 3.3/5.
The two tools have clearly distinct purposes: temporal_peek reads state without advancing, while temporal_tick advances the clock and returns a snapshot. No overlap or ambiguity.
Both tools follow the same verb_noun pattern with the temporal_ prefix, making naming predictable and consistent.
With only 2 tools, the server feels minimal for state management. While the focused scope is acceptable, it may lack additional operations like reset or query that could be expected.
The tools cover the core temporal operations: peeking and advancing state. Minor gaps exist (e.g., no reset or manual override), but the surface is functional for the stated purpose.
Available Tools
2 toolstemporal_peekInspect
Read 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.
| Name | Required | Description | Default |
|---|---|---|---|
| tz_name | No | ||
| client_id | No | ||
| thread_key | No | ||
| tz_offset_minutes | No |
temporal_tickInspect
Advance 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.
| Name | Required | Description | Default |
|---|---|---|---|
| tz_name | No | Display name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header. | |
| client_id | No | Namespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'. | |
| thread_key | No | Stable thread identifier within this client. For claude.ai web use the conversation ID; for other MCP clients any caller-stable string. If omitted, falls back to the Mcp-Session-Id header. | |
| tz_offset_minutes | No | Caller's UTC offset in minutes (e.g. -360 for MDT). Used for day_rollover detection and header formatting. Defaults to 0 (UTC) so day rollover is always honest even if the caller forgets to pass one. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.