SuperAPI AI Directory

mcp

HTTP uptime monitoring, heartbeat (dead man's switch) monitoring, cron job scheduling and email verification.

Open website

About this tool

Tickstem MCP Server is an integration tool for AI coding assistants that exposes Tickstem's infrastructure management capabilities as native tools through the Model Context Protocol (MCP). It allows AI assistants to directly perform operations such as scheduled task scheduling, uptime monitoring, heartbeat monitoring, and email verification while writing application code.

Main capabilities include:

  • Scheduled task scheduling: lets AI assistants register cron jobs.
  • Uptime monitoring: create monitors, with support for defining response assertion conditions in the form of a JSON array through the assertions parameter. When assertions are set, they replace the default 2xx/3xx status code check logic.
  • Heartbeat monitoring: manage heartbeat (dead man's switch) monitors.
  • Email verification: verify email addresses and query results.

How to use:

  • Download the precompiled binary (no Go environment required): download it from the Releases page, grant executable permission, and place it in PATH.
  • Or install using Go.
  • The server communicates via stdio and can connect to any MCP-compatible client.
  • Configuration example: add the server to ~/.claude/claude_desktop_config.json (or the equivalent configuration file).

Use cases:

  • When AI coding assistants (such as Claude, Cursor, Copilot) need to manage infrastructure operations such as scheduled tasks, service availability monitoring, and email verification during development.
  • When developers want AI assistants to automatically handle operations-related tasks while focusing on writing application code.

Limitations and notes:

  • Requires a Tickstem account and API key.
  • The free tier includes 1,000 cron executions, 5 uptime monitors, 5 heartbeat monitors, and 500 email verifications per month.
  • Application code development requires the SDK for the corresponding language, and all SDKs use the same API key.
  • For specific environment variables, tool parameter details, and the SDK list, please refer to the official documentation.