CountLink
v1.0.0Shared countdown timers that stay in sync on every screen — no account, any number of viewers.
Endpoint health
online- Last checked
- 11/20/2026, 5:17:23 AM
- Latency
- 90 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.countlink%2Fcountdown
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.countlink/countdown": {
"url": "https://countlink.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
Create a chained agenda of timed segments
create_agenda
Create a CountLink agenda: an ordered sequence of named, timed segments (intro, talk, break, Q&A) that starts now and advances from one to the next on its own, on every screen that opens the link, with no server involved. Use this when someone describes a meeting, workshop, lesson or event as a sequence of parts with lengths — including when they give you a total and a list of topics and expect you to split it ("an hour, four topics"): do the split yourself, then pass the resulting segments here. By default it starts immediately; pass start_at for something scheduled ahead ("our workshop starts at 9:15 tomorrow") — the link works right away, showing a live countdown to the start rather than the first segment, and switches over on its own at the scheduled instant, in sync on every screen that opened it. Returns the shared link plus a run sheet with the wall-clock start and end of each segment, and an .ics calendar file (one event per segment) in structuredContent.ics — offer it if the person might want the agenda on their calendar. For a single countdown use create_timer instead.
Schema valid · SHA-256 f4879dca93b4…
View input schema
{ "type": "object", "properties": { "segments": { "type": "array", "minItems": 1, "maxItems": 24, "description": "The segments in running order. Each has a duration (same grammar as create_timer: \"10m\", \"1h\", \"90s\", \"5:00\", or a plain number of minutes) and an optional short label. 1–24 segments; the whole agenda must fit in 99h59m59s.", "items": { "type": "object", "properties": { "duration": { "type": "string", "description": "How long the timer runs. Accepts \"25m\", \"1h30m\", \"90s\", \"5:00\", \"1:30:00\", or a plain number read as minutes (\"45\"). A setup link or OBS overlay holds up to 99h59m59s. With start_now or embed_on_website, longer countdowns of up to 366 days are fine: \"10d\", \"10 days\", \"10d 6h\" or \"240h\"." }, "label": { "type": "string", "description": "Optional name for the segment, e.g. \"Intro\" or \"Break\". Keep it short." } }, "required": [ "duration" ] } }, "start_at": { "type": "string", "description": "Optional ISO-8601 instant for a scheduled start, e.g. \"2026-09-08T09:15:00Z\" or with a local offset like \"2026-09-08T09:15:00+01:00\". Omit to start immediately. A start_at already in the past is just treated as already running from that instant." } }, "required": [ "segments" ] }
Connections
streamable-http
https://countlink.app/mcp