temporal-mcp

A small MCP server that provides wall-clock awareness for LLM agents by tracking elapsed time between turns, detecting day rollovers, and identifying fresh threads. It exposes two tools, temporal_tick and temporal_peek, to help models understand temporal context in conversations.

Visit MirrorEthic

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by MirrorEthic

You need:Grab a Client ID + Client Secret, paste into Custom Connector, done.Pick any opaque string as your token and use: POST https://temporal-mcp.dev/mcp Authorization: Bearer <any opaque string you choose>

MCP endpoint (Streamable HTTP)

https://temporal-mcp.dev/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 1 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 3:23 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Detect day rollover between conversation turns
Calculate elapsed time since the last user message
Identify if a chat thread is fresh or resumed

Source and maintenance

Community listingRegistry 0.2.0

mcp-registry: io.github.MirrorEthic/temporal-mcp@0.2.0 Source repository Project website

Maintenance checked: Nov 6, 2026, 3:14 PM UTC

Protocol and capabilities

Server: temporal-mcp 0.2.0
MCP protocol negotiated in check: 2025-06-18
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

2 advertised

temporal_tick

Advertised by the server during the last successful anonymous check.

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.

temporal_tick input schema

{
  "type": "object",
  "properties": {
    "tz_name": {
      "type": "string",
      "description": "Display name for the timezone (e.g. 'MDT'). Cosmetic; appears in the rendered header."
    },
    "client_id": {
      "type": "string",
      "description": "Namespace tag (e.g. 'caweb', 'cursor'). Defaults to 'mcp'."
    },
    "thread_key": {
      "type": "string",
      "description": "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": {
      "type": "integer",
      "description": "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."
    }
  }
}

temporal_peek

Advertised by the server during the last successful anonymous check.

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.

temporal_peek input schema

{
  "type": "object",
  "properties": {
    "tz_name": {
      "type": "string"
    },
    "client_id": {
      "type": "string"
    },
    "thread_key": {
      "type": "string"
    },
    "tz_offset_minutes": {
      "type": "integer"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 285 ms
95th percentile latency: 285 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 3:23 PM UTC · probe · passed · 285 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http temporal-mcp-mcp https://temporal-mcp.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add temporal-mcp-mcp --url https://temporal-mcp.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable temporal-mcp-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "temporal-mcp-mcp": {
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "temporal-mcp-mcp": {
      "type": "streamableHttp",
      "url": "https://temporal-mcp.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start temporal-mcp-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "temporal-mcp-mcp": {
      "type": "http",
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http temporal-mcp-mcp https://temporal-mcp.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://temporal-mcp.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "temporal-mcp-mcp": {
      "serverUrl": "https://temporal-mcp.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like temporal-mcp from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 8,317