list_jobsLABSCO SUMMARY
The monitoring you keep meaning to set up, set up while you code.
Scheduling and uptime checks usually get postponed because they mean leaving the editor for a dashboard. Here registering a job, adding a monitor with assertions and reading execution history are all tool calls — and pause and resume exist, so deploys do not have to mean deleting and rebuilding.
What it is
A Go MCP server for Tickstem, exposing cron scheduling, uptime monitoring and heartbeat monitoring as tools over stdio.
What you get
- Cron jobs across their whole life: registered with a name, schedule and endpoint; listed; fetched by id; updated field by field; paused; resumed; deleted
- Execution history for a job, most recent first, for when a schedule stopped firing and you need to know when
- Uptime monitors created with optional response assertions, then listed with status, URL, interval, SSL expiry and the assertions in force
- Monitor checks listed, so a flapping monitor can be read check by check
- Monitors paused and resumed, which is what you want during a planned deploy rather than deleting them
- Heartbeat monitors created and listed, for jobs that report in rather than being polled
Requirements
A Tickstem API key in TICKSTEM_API_KEY. Prebuilt binaries are published for macOS (Apple Silicon and Intel), Linux (Intel and ARM) and Windows, so Go is not required to run it.
Setup effort
One command plus a key — go install github.com/tickstem/mcp/cmd/tsk-mcp@latest, then supply credentials
USE CASES
01
Scheduling the endpoint you just wrote
Register the cron job with its name, schedule and endpoint without leaving the code you were writing.
02
Working out why a scheduled job stopped doing its work
Pull the execution history newest-first and read the job's current definition alongside it.
03
Silencing alerts through a deploy
Pause the job and the monitor for the window, then resume both, instead of deleting and recreating them.
04
Watching a service for more than a 200
Create a monitor with response assertions so a page that returns wrong content still counts as down.
05
Catching an SSL certificate before it expires
List the monitors and read the SSL expiry alongside status, URL and interval in one view.
06
Watching a job that runs somewhere you cannot poll
Create a heartbeat monitor so a batch job that fails to check in raises the alarm.
07
Clearing out schedules nobody owns
List everything registered, then delete the jobs and monitors that no longer have a purpose.
26 tools
Listed in project docs. Your client may show a different list.
get_jobregister_jobupdate_jobpause_jobresume_jobdelete_joblist_executionslist_monitorscreate_monitorget_monitorpause_monitorresume_monitordelete_monitorlist_monitor_checkslist_heartbeatscreate_heartbeatget_heartbeatupdate_heartbeatpause_heartbeatresume_heartbeatdelete_heartbeatping_heartbeatlist_heartbeat_pingsverify_emaillist_verify_historyBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- tsk-mcp on PATH
- TICKSTEM_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
go install github.com/tickstem/mcp/cmd/tsk-mcp@latestMCP Clients
Claude Code, Claude Desktop
JSON
{
"mcpServers": {
"tickstem": {
"command": "tsk-mcp",
"env": {
"TICKSTEM_API_KEY": "<YOUR_TICKSTEM_API_KEY>"
}
}
}
}
