Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like temporal-mcp.
https://temporal-mcp.dev/mcpuvx temporal-mcpHeaders: Authorization
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-mirrorethic-temporal-mcp": {
"command": "uvx",
"args": [
"temporal-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.
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-...'
temporal-mcp is an MCP server for Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.. It supports STDIO, HTTP transport.
Use the generated config in Install. This server runs with uvx temporal-mcp; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://temporal-mcp.dev/mcp.
Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://temporal-mcp.dev/mcp.
Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://temporal-mcp.dev/mcp.
Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://temporal-mcp.dev/mcp.
temporal-mcp uses STDIO, HTTP transport. Endpoint: https://temporal-mcp.dev/mcp.
temporal-mcp inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
temporal-mcp is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
temporal-mcpstdio | pypi | 0.2.0 | None advertised |