Monitors
Delete a monitor and stop the recurring charge
Removes the monitor and its check history. The scheduled checks stop, and so does the only recurring cost on the platform.
delete_monitor
What it is
The job: Turn off a watch you no longer need.
Monitors are the one part of Twin Browser that spends credits without you calling anything, so deleting them is the one cleanup that has an ongoing cost attached. The monitor and its check history are removed together.
If you want to stop the checks but keep the definition, PATCH the monitor to active: false over REST instead — the MCP surface has delete but not pause.
The call
Call it exactly like this.
Copied from the tool's registration and the route handler — not paraphrased.
// MCP tool call — server "twin-browser"
{
"tool": "delete_monitor",
"arguments": {
"id": "…"
}
}curl -X DELETE "https://twin-browser.com/api/v1/monitors/MONITOR_ID" \
-H "Authorization: Bearer $TWIN_API_KEY"| Parameter | Type | What it does |
|---|---|---|
| id* | string | The monitor id, from list_monitors. |
Returns
{ "deleted": true }What it costs
Free
Deleting costs nothing and stops the recurring per-check charge from the next tick onward.
See the full rate cardWhich one
When a different tool is the right call.
The honest answer is often the neighbouring tool. These are the trades.
Questions
delete_monitor, answered.
- Can I pause a monitor instead of deleting it?
- Yes, over REST: PATCH /api/v1/monitors/{id} updates active, interval, callback, selector and watch spec. The MCP tool set covers create, list, history and delete, so a pause is one of the things worth reaching for the REST API for.