Cronitor hosted MCP

Cronitor's hosted MCP server exposes the same resources as the REST API, including alert destinations. Agents must never echo integration secrets.

Authentication

Connect with an API key or OAuth. OAuth sessions carry the signed-in user's role: read-only users can list integrations and poll a connection; users who can manage integrations can also create, connect, and delete destinations. API keys need integration:read or integration:write.

Integrations

These six tools manage notification destinations. They do not return Slack webhook URLs, PagerDuty keys, webhook passwords, or api_key values.

list_integrations[read-only]

get_integration_services[read-only]

create_integration[write]

connect_integration[write]

check_integration_connection[read-only]

delete_integration[write]

list_integrations accepts optional service, label, page, and page_size. create_integration requires service, name, and fields (Slack and PagerDuty return connect_required). connect_integration starts a Slack or PagerDuty browser session — hand authorize_url to the human. check_integration_connection polls by token. delete_integration soft-deletes by service and label; in-use destinations error unless force is true.