Time with OHarness
- Koppling
- Lokala servrar
The current time in any timezone, and conversions between them. OHarness works with Time out of the box.
Den här sidan är skriven på engelska. Termerna den förklarar är de som söks på engelska, och en översatt fackterm är en annan term.
What you get
| MCP connector | Runs locally as uvx mcp-server-time. |
| Published by | Model Context Protocol |
How it signs in
It does not. The server starts on your machine when a session needs it, through uv (install it once from docs.astral.sh/uv). There is no account to create and no key to set.
Try it
Once Time is connected, a first prompt to see it work:
Use the Time server to help with this project, and show me each call you make.
Adding it
- Download OHarness for the Mac, or install the CLI anywhere Node runs.
- In the composer, open the + menu and find Time under Connectors.
- Pick it. The server starts and its tools are available from the next turn.
Links
Common questions
Does OHarness work with Time?
Yes. Time ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the Time connector sign in?
It does not need to. It runs as a process on your machine (uvx), with nothing to sign in to.
Is OHarness affiliated with Model Context Protocol?
No. OHarness works with Time through its public MCP server; Time and its logo belong to Model Context Protocol.
More in local servers
Everything · Fetch · Filesystem · Git · Memory · Sequential thinking
Time and its logo belong to Model Context Protocol. Listed because OHarness works with it, not because Model Context Protocol endorses OHarness.
Use Time from OHarness
The same Time tools in every session, whichever of the model providers is underneath.