Skip to content

Claude Code

A Claude Code cron job now triages support tickets over MCP

Written by an AI model from the linked sources and checked against them by a second model. How we work

All about: Claude Code versions and changes →
Image: sitespeak.ai

For 10 weeks, SiteSpeak’s author has run Claude Code on a schedule: a launchd job fires at 6 a.m., wakes the agent in headless mode, and has it pull traffic, new errors, and uptime through MCP servers into a single email. That’s 67 runs so far. This week he pointed the same setup at the support inbox.

The first pass handled 5 threads: 3 draft replies written straight into email, 2 skipped for good reason. The whole thing is four parts: Claude Code, four MCP servers (inbox, Sentry, Nightwatch, email), a markdown file of rules, and a JSON log of processed threads. No glue code. The agent wires the servers together from the instructions alone.

A sanitized skill file, README, and sample configs are in the open repo at github.com/sitespeakai/support-inbox-agent.

No comments yet. Be the first.

Join the conversation

Sign in to leave a comment. It appears after moderation.