
Tickstem
dev.tickstemPublished by tickstem.devv1.0.0Updated Oct 27, 2026
Tickstem developer tools — manage cron jobs and verify emails from your AI coding assistant.
Overview
Tickstem's local MCP server lets an AI assistant create and manage cron jobs, uptime and heartbeat monitors, and verify email addresses.
- What you can do
- List, create, update, pause, resume and delete cron jobs, and read their execution history
- Create and manage uptime monitors with response assertions on status code, response time and body, and list recent checks
- Create and manage heartbeat (dead-man's switch) monitors, ping them and list recent pings
- Verify email addresses for syntax, MX records, disposable domains and role-based prefixes, and list past verification results
- When to use it
- Useful when you want your coding assistant to set up scheduled jobs, uptime or heartbeat monitoring and email checks for an app while you write code, instead of switching to a separate dashboard.
- Requirements
- Runs as a local binary (pre-built for macOS, Linux and Windows, or installed with Go) and speaks MCP over stdio. Requires a Tickstem API key in the TICKSTEM_API_KEY environment variable; TICKSTEM_BASE_URL optionally overrides the API base URL. Network access to the Tickstem API is needed.
Installation
In SourceWeft
- Open Tickstem in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
tickstem/mcp
MCP server for Tickstem — exposes cron job scheduling, uptime monitoring, heartbeat monitoring, and email verification as native tools for AI coding assistants (Claude, Cursor, Copilot, and any MCP-compatible agent).
Let your AI assistant register cron jobs, create uptime monitors with response assertions, manage heartbeat monitors, verify email addresses, and query results — while you write the app code.
Install
Download a pre-built binary (no Go required):
Download from Releases, make executable, and place on your PATH:
Or install with Go:
Quick start
The server speaks the Model Context Protocol over stdio — connect it to any MCP-compatible client.
Claude Code
Add to your ~/.claude/claude_desktop_config.json (or equivalent):
Available tools
Cron jobs
Uptime monitoring
Response assertions
create_monitor accepts an assertions parameter — a JSON array of conditions that must all pass for a check to be considered up. When assertions are set they replace the default 2xx/3xx logic.
Heartbeat monitoring
Email verification
Environment variables
Local development
SDKs
The MCP server handles infrastructure management from your AI assistant. For application code, use the SDK that matches your language:
All SDKs use the same API key.
Get an API key
app.tickstem.dev — free tier includes 1,000 cron executions, 5 uptime monitors, 5 heartbeat monitors, and 500 email verifications per month.
License
MIT
Source: README.md at commit baf970d
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts