"author:sitewarm" matching MCP servers:

Enables an MCP client to inspect sites, warm runs and their results, cache status reports and schedules through the API, and — only when writes are explicitly enabled and confirmed — to trigger or cancel warm runs and create, update or delete schedules. Read-only operation is the safe default, with API-key scopes, redaction, idempotency and no retries or redirects.