mcpbeat

temporal-mcp MCP Server

io.github.MirrorEthic/temporal-mcp
answering

temporal-mcp is answering right now. Last checked 9 min ago. 55 installs a week from pypi. It exposes 2 tools. Last commit 13 May 2026.

Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

Installs per day peak 31 · avg 10 · -19% w/w
a month agotoday
Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
129 ms
Response time
average over 24h
55
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add temporal-mcp --transport http https://temporal-mcp.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "temporal-mcp": {
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.temporal-mcp]
url = "https://temporal-mcp.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "temporal-mcp": {
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "temporal-mcp": {
      "url": "https://temporal-mcp.dev/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

temporal
temporal_peek
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_tick
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.

Endpoints

URLTransportStateLatencyChecked
https://temporal-mcp.dev/mcp streamable-http answering 251 ms 9 min ago

temporal-mcp — questions

Answers built from our own checks of this server.

What can temporal-mcp do?
It exposes 2 tools, read directly from the server on our last check. Among them: temporal_peek, temporal_tick. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is temporal-mcp working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 129 ms. The bar chart above shows every period we have measured.
How do I connect temporal-mcp?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does temporal-mcp need an API key?
No. temporal-mcp completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is temporal-mcp?
It answers our handshake in 129 ms on average, which is faster than 78% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use temporal-mcp?
The pypi package temporal-mcp was installed 55 times in the last week. Week over week that is -19%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is temporal-mcp open source?
Yes — it is published under the MIT licence, written in TypeScript and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.