Subscribers API - Squasher

Use the Subscribers API when an operator needs subscriber visibility for a status page. Subscriber reads are intentionally not exposed through hosted MCP by default.

Operations

Operation	Method and path	Purpose
`subscribers.list`	`GET /v1/projects/{project_id}/status-pages/{status_page_id}/subscribers`	List subscribers with notification channel and component scope.
`subscribers.get`	`GET /v1/projects/{project_id}/status-pages/{status_page_id}/subscribers/{subscriber_id}`	Get one subscriber.
`subscribers.delete`	`DELETE /v1/projects/{project_id}/status-pages/{status_page_id}/subscribers/{subscriber_id}`	Delete a subscriber for operator-driven cleanup.

CLI and MCP

Use squasher subscribers ... or the REST API. Hosted MCP hides subscriber operations; do not assume search("subscribers") will return runnable operations.

Agent handoff

Inspect status-page subscribers for project <project_id> and status page <status_page_id>. Use the REST API or CLI, summarize subscriber ids and channel scope, and ask before deleting any subscriber.

Related: Status pages API.