MCP · LOCAL DEVELOPER PREVIEW

Keep your agent
on your time.

A conversation can start with “what time works?” Give a compatible assistant the tools to answer across cities and work with your desktop clocks.

01 / READ & COMPARE

One moment. Many places.

Read the current time in selected zones, or compare a specified moment across cities. TimeSlider uses time-zone rules to account for daylight-saving changes.

“When it's this moment in London, what time is it in Bangkok?”
02 / DESKTOP CONNECTION

Your clocks, close by.

With the optional local desktop connection enabled, an agent can list, add, update or remove supported saved clocks. Changes use the running app's state and respect its Free or Pro limits.

“Add Berlin to my desktop clocks.”
03 / PRO PLANNING

Find a shared window.

Use saved available hours to explore overlap for a group. This follows the app's Pro planning access. Entered hours describe preferences; they do not establish calendar availability.

“Find shared hours for my group.”

START LOCALLY

A connection you choose.

This release is source-level developer access. It is not a hosted account connection or a one-click store download. A compatible MCP client launches the local server. Reading the app's saved clocks also requires the opt-in bridge and the running desktop development app.

  1. Install the MCP server's dependencies from the repository's mcp/ directory.
  2. Configure a compatible agent to launch the repository's local MCP server. Use the included README for the exact command and client configuration.
  3. Enable the desktop agent bridge when starting the desktop development app if you want saved-clock access. Stateless time-zone comparisons do not require this connection.
  4. Begin with a read request. Review requested clock changes in your agent and confirm the result in TimeSlider.

Setup commands, tool descriptions and tests are included with the repository. Client support and configuration vary; this page does not claim every assistant is connected or that hosted MCP is available.

YOUR CLOCKS. YOUR CHOICE.

Know what you share.

The desktop connection runs locally with authentication and exposes clock tools. It does not give the agent shell commands, calendar event contents or motor controls. Data your agent receives can enter its conversation and be processed by its model provider under that agent's settings.

Keep the desktop bridge disabled when you do not want app access. The current MCP connection does not synchronize accounts or control a phone, watch or physical clock.

Read about your data ↗

HOWARD DONDRELL · POWERED BY TIMESLIDER

A future place for the same clocks.

A connected Howard Dondrell device could eventually show the same clocks you organize with an agent. That would need a tested device companion, firmware and a connection protocol. No physical device is connected today, and automatic mechanical reset is a separate engineering project.

The hardware project starts with concepts and a free waitlist. Agent access is useful for the software on its own; owning a clock is not required.

Explore the hardware concepts ↗