Ask Claude Code what to monitor — then set it up in Holter.
Holter runs an MCP server. Connect Claude Code (or any MCP-capable agent) with a team-scoped token, and it reads your repo locally to propose the monitors your project needs. Holter never sees your source — only the monitors your agent sends, which you approve.
No credit card · free plan · up and watching in minutes.
$ agent scanning repo…
✓ found
→ 4 monitors proposed · review & apply
The problem
You already use Claude Code to understand your codebase. But wiring up monitoring still means combing through crons, queues, and health checks by hand and hand-writing heartbeat calls — so most projects get it half right once and never revisit it.
Set up in three steps
Get a team-scoped MCP token
Create a token in Holter — it acts only within your Holter team, with no cloud keys or server access.
Connect your agent
Add Holter’s MCP server to Claude Code (or your MCP-capable agent) and ask it to review the repo for things worth monitoring.
Review and apply
Your agent proposes monitors and heartbeat code locally. You approve what gets created; Holter only receives the approved monitors.
What Holter does
Point your agent at Holter’s MCP server with a team-scoped token. Your agent reads the repo on your machine, finds the crons, queues, endpoints, and domains worth watching, and proposes monitors plus heartbeat code for you to review. Holter only receives the monitors you approve — it never gets access to your source or your servers.
- ✓ Your agent reads the repo locally — Holter never gets your source
- ✓ Proposes crons, queues, health checks, and domains to watch
- ✓ Works with a team-scoped token, never your cloud keys
- ✓ Your agent shows you every monitor before it applies it
Simple, transparent pricing
Agent-assisted setup works on every plan, including Free. Pro is where faster checks and larger monitor counts matter as you add more, from $15/mo.
Free plan needs no card. Every paid plan includes a 14-day free trial.
See full pricingQuestions, answered
No. Your agent runs locally and reads your repo on your machine. Holter only receives the monitors and heartbeat URLs your agent proposes, through the token you control.
Any MCP-capable agent — Claude Code, Cursor, and others. You connect Holter’s MCP server with a team-scoped token.
It is scoped to your Holter team and acts only on your Holter account — it carries no access to your servers, cloud, or code.
No. The MCP flow is an optional faster path; you can set up every monitor by hand in the dashboard.
Ask Claude Code what to monitor — then set it up in Holter.
No credit card required. Free plan available.
Get your MCP token