SponsorSubmit a toolSubscribe

Does Time (reference) work with Claude Desktop?

Yes. Time (reference) passed every step of our test in Claude Desktop on Oct 19, 2026: it installed, connected, its tools were visible, and an agent used it to finish a real task.

Result

ResultPassed
Date testedOct 19, 2026
Plan tested onNot recorded for this run
App versionClaude Desktop 2.37337.1 (Linux beta)
Server packagemcp-server-time 2026.10.19 (pinned in the command we ran)
Connect timeconnected in 0.7s

Steps

  1. install OK
  2. connect OK
  3. tools visible OK
  4. agent task: time zones OK

Test note: server wrapped in harness/scripts/mcp_tee.py to record JSON-RPC; prompts typed via xdotool; tool Allow pop-ups approved by the operator for test servers only; model = app default

From our own harness run, not the maker’s claims. How we test.

Versions tested

Claude Desktop 2.37337.1 (Linux beta) · mcp-server-time 2026.10.19 (pinned in the command we ran) · connected in 0.7s · tested Oct 19, 2026

Server package and resolved dependency versions: not recorded for these runs (our harness records them from Oct 19, 2026 on).

What happened in this run

Install config we used

{
 "command": "uvx",
 "args": [
  "mcp-server-time"
 ]
}

Connection check

initialize seen in tee log after app restart

Tools check

tools/list answered (tee log)

Agent task: time zones

  • 1 calls reached the server
  • Agent’s answer (excerpt): It's currently 14:57:40 UTC on Monday, October 19, 2026.

Raw details from our harness log for this run. Secrets redacted.

Set it up in Claude Desktop

Copy-paste config for every app is on the Time (reference) page. Not connecting? Claude Desktop MCP troubleshooting.

Other apps we tested it in: Claude Code (passed) · Cursor (passed) · ChatGPT (Codex) (passed).

All MCP servers tested in Claude Desktop

Sponsors
+Sponsor this space