Mcp
Manage Tickstem cron jobs and verify email addresses from your AI assistant without leaving the editor.
Overview
dev.tickstem/mcp is an MCP server for the Operate phase that lets agents manage Tickstem cron jobs and verify emails from the coding environment.
What is this MCP server?
- Manage cron jobs through MCP tools from Tickstem
- Verify email addresses via the same MCP server
- Aimed at AI coding assistants (Claude Code, Cursor-class clients)
- Open-source Tickstem MCP package on GitHub (tickstem/mcp)
- Developer-tooling focus—not a full marketing automation suite
- MCP server version 1.0.0
- Two capability areas: cron job management and email verification
- Source repository: github.com/tickstem/mcp
Community signal: 1 GitHub stars.
What problem does it solve?
Jumping between your repo, a cron dashboard, and email-validation APIs breaks flow when you only need to schedule a job or confirm an address is real.
Who is it for?
Indie SaaS builders already using or evaluating Tickstem who want MCP-driven cron and email checks from Claude Code or Cursor.
Skip if: Builders who need a full ESP, marketing automation, or cron without any Tickstem account setup.
What do I get? / Deliverables
After registration, your agent can create or adjust Tickstem cron jobs and run email verification in the same session as your shipping code.
- Cron job definitions or updates managed via MCP tool calls
- Email verification results for addresses you submit through the server
Recommended MCP Servers
Journey fit
Scheduled jobs and production email hygiene are ongoing runtime concerns, so the canonical shelf is Operate where infra and background work live. Infra subphase covers cron scheduling, background tasks, and operational hooks agents call after the product is live.
How it compares
MCP bridge to Tickstem cron and verification APIs, not a standalone agent skill for writing crontab files only locally.
Common Questions / FAQ
Who is dev.tickstem/mcp for?
It is for solo developers and small teams who use AI coding assistants and Tickstem for scheduled tasks or email validation in production workflows.
When should I use dev.tickstem/mcp?
Use it in Operate when you configure recurring jobs, fix schedules after deploy, or validate emails during signup flows without leaving the agent.
How do I add dev.tickstem/mcp to my agent?
Add the dev.tickstem/mcp server from the MCP registry or GitHub schema to your client’s MCP configuration and supply Tickstem credentials your tools require.