Timer MCP servers and APIs compared
A timer link opens a display. A server timer schedules work.
Choose the interface that matches the job.
Reviewed October 18, 2026. Written by Gotoh Industries LLC, the operator of Eggtimer.app. Competitor entries describe their official documentation; we have not independently benchmarked their infrastructure or purchased their paid plans. “Not established” means the reviewed sources do not establish a capability, not that it is absent.
| Task | Eggtimer.app | timer.ly | CountdownShare API |
|---|---|---|---|
| Create a timer URL from an assistant | Seven public MCP tools; validated duration and recipe links. No key. | Anonymous MCP link tools for durations, dates and count-up. | REST API with authenticated timer creation and publishable outputs. |
| Run repeated, labeled stages without an open tab | Finite server recipes, step/cycle events, immutable timeline and run cancellation. Scoped workspace key. | Not established in reviewed MCP reference. | Recurring countdowns documented; a phase-by-phase recipe interface is not established in reviewed overview. |
| Timer lifecycle | One-shot duration/deadline timers; finite routines; read, cancel and retained event history. No server pause/resume or schedule edits. | Link construction; multilingual dates and holiday discovery. | Pause/resume, revisions, recurring/personalized timers, signed webhooks and replay documented. |
| Destinations | Zapier HTTPS Catch Hooks only. Independent event outboxes; bounded retries and freshness. | Server webhook delivery not established in reviewed sources. | Registered webhook destinations and signed delivery. |
| Cost and access | Browser and public links free; workspace automation is a bounded free plan. | States free, without signup or ads. | Free sandbox: 100 test timers/month; no publishing. Production starts at $9/month for 1,000 timers. |
Where Eggtimer fits
Use Eggtimer when the same routine should work as a lightweight browser display and as an inspectable server workflow. Recipe JSON supplies the steps; the public API builds its preview link; the authenticated API runs it and returns step/event addresses. The URL contains no key. Server records require the owning workspace key and have explicit retention.
For localized holidays and count-up links, timer.ly documents broader coverage. For revisioned marketing countdowns, signed generic webhooks and replay, CountdownShare documents a broader server lifecycle. These are meaningful differences, not an overall league table.
MCP setup and verification
https://eggtimer.app/api/mcp constructs links. https://eggtimer.app/api/mcp/server adds workspace scheduling and status with a Bearer key. Eighteen workspace tools expose operations individually, with titles and read/write hints. Transport and setup · OpenAPI. Protocol tests and production probes do not prove compatibility with every assistant or guaranteed discovery.
Primary sources
timer.ly overview · timer.ly MCP reference · CountdownShare API overview · CountdownShare API pricing.