Statuscake
StatusCake is a website monitoring platform that provides observability for applications, offering features like uptime monitoring, page speed monitoring, SSL monitoring, and more.
Verdict
Common use cases
- Pull uptime test results during incident triage
- Create new monitors from chat during deploys
- List all PageSpeed tests before optimization sprint
- Delete obsolete heartbeat checks after decommission
- Audit contact groups when rotating on-call
Integration
- Vendor
- Statuscake
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
statuscake
Tools
- Delete Contact Groupdestructive
Tool to delete a contact group. use when you need to remove an existing contact group by its id after confirming its existence.
- Delete Testdestructive
Tool to delete a statuscake test. use when you need to remove a test by its id after it's no longer needed.
- Get All Contact Groups
Tool to retrieve all contact groups. use when you need to list existing contact groups in statuscake after authenticating.
- Get All Monitoring Locations
Tool to retrieve a list of all monitoring locations. use when you need to display or choose from available statuscake locations.
- Get All PageSpeed Tests
Tool to retrieve all pagespeed tests. use when you need to list existing pagespeed performance tests in statuscake after authenticating.
- Get All Tests
Tool to retrieve a list of all tests. use when you need to list your monitoring tests in statuscake.
- Get Contact Group Details
Tool to retrieve details of a specific contact group. use when you need group metadata by providing its id. example: "get details for contact group 12345".
- Get Heartbeat Checks
Tool to list heartbeat checks. use when you need to retrieve all heartbeat monitoring tests for your account.
- Get SSL Check Details
Tool to retrieve details of a specific ssl check. use when you need configuration and status of an ssl test by providing its id. example: "get ssl check details for 123".
- Get SSL Checks
Tool to retrieve a list of ssl checks. use when you need to list all ssl tests for your account.
- Update Contact Group
Tool to update an existing contact group. use when you have the contact group id and want to change its configuration.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Browse MCP Servers. 2. Search for StatusCake and click Connect. 3. You'll be prompted to paste your StatusCake API key — generate one by logging into StatusCake, going to User Details > API Keys, and creating a new key with full permissions. 4. Copy the key and paste it into Switchy's auth modal, then click Authorize. 5. Switchy confirms the connection by listing your monitoring locations. 6. Open any Space, type '@StatusCake get all tests' and send — the AI will return your active monitors, proving the integration works. 7. From now on, @mention StatusCake in any message to invoke its tools; the AI decides which tool fits your request and returns structured results inline.
What teammates see: by default, memories from Statuscake are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Monitors
@StatusCake show me all active monitoring tests in our account right nowOpen in a Space →
Check PageSpeed Tests
@StatusCake get all pagespeed tests and tell me which pages we're monitoring for performanceOpen in a Space →
Find Monitoring Locations
@StatusCake what monitoring locations are available for uptime checksOpen in a Space →
Review Contact Groups
@StatusCake list all contact groups and show me who's in each oneOpen in a Space →
Audit Heartbeat Checks
@StatusCake show me all heartbeat checks and their last ping timesOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@statuscake show me all active uptime tests and their current status
Here are your 7 active uptime tests: • example.com homepage (ID: 8472619) – Up, last checked 2 min ago from London • api.example.com/health (ID: 8472620) – Up, last checked 1 min ago from New York • checkout.example.com (ID: 8472621) – Down (503), last checked 30 sec ago from Sydney • staging.example.com (ID: 8472622) – Paused • blog.example.com (ID: 8472623) – Up, last checked 3 min ago from Frankfurt • cdn.example.com (ID: 8472624) – Up, last checked 1 min ago from Singapore • admin.example.com (ID: 8472625) – Up, last checked 2 min ago from London This is an illustrative example showing typical test metadata returned by the Get All Tests tool.
This example demonstrates read-only monitoring visibility. The MCP requires a valid API key with read permissions. Real output includes check intervals, response times, and alert configurations. Useful for daily standup reviews or incident triage, but won't show historical downtime patterns without additional queries.
@statuscake delete test ID 8472622 for staging.example.com since we've decommissioned that environment
Test deleted successfully. Removed uptime test: • ID: 8472622 • URL: staging.example.com • Status before deletion: Paused This test is now permanently removed from your StatusCake account and will no longer consume test quota or generate alerts. This is an illustrative example of the Delete Test tool's confirmation response.
This example shows a destructive action with immediate effect. The MCP requires API key permissions for test deletion. There's no undo — once deleted, historical data for this test is lost. Always verify the test ID before deletion. Consider pausing tests instead of deleting them if you might need historical uptime data later.
@statuscake list all contact groups, then explain which one I should use for critical production alerts based on their current membership
You have 3 contact groups configured: **1. On-Call Engineers (ID: 45231)** • 4 members: email, SMS, Slack webhook • Includes: sarah@example.com, mike@example.com, +1-555-0123, Slack #incidents **2. Dev Team (ID: 45232)** • 2 members: email only • Includes: dev-team@example.com, qa@example.com **3. Management (ID: 45233)** • 1 member: email • Includes: reports@example.com **Recommendation:** Use "On-Call Engineers" (ID: 45231) for critical production alerts. It's the only group with SMS and Slack integration for immediate notification, and includes 4 escalation paths. The other groups lack real-time channels and would delay incident response. This is an illustrative example combining the Get All Contact Groups tool with AI reasoning.
This example demonstrates synthesis — the MCP fetches raw contact group data, then the AI analyzes notification channels and recommends the best fit. Requires read permissions on contact groups. The recommendation quality depends on how descriptive your group names and member details are in StatusCake. Useful for alert routing decisions during infrastructure changes.
Use-case deep-dives
When StatusCake MCP speeds up outage triage
A 6-person engineering team runs a SaaS product with 40 uptime monitors across three regions. During an incident, the on-call engineer needs to check which tests are failing, verify contact group escalations, and temporarily disable noisy heartbeat checks while they debug. The StatusCake MCP wins here because it surfaces all 11 monitoring operations in one AI workspace—no context-switching to the StatusCake dashboard. The engineer asks Switchy to list failing tests, pull contact group details for the pager rotation, and pause specific checks. This works until you hit 200+ tests; at that scale, the MCP's list-all pattern gets slow and you're better off using StatusCake's native filtering. For small-to-midsize teams running under 100 monitors, this MCP turns incident triage into a conversation.
How agencies use this MCP for new client setups
A 4-person dev shop onboards 2-3 new clients per month, each needing uptime monitors, PageSpeed tests, and custom contact groups. Traditionally, this means logging into StatusCake, clicking through forms, and copy-pasting client emails. The StatusCake MCP collapses that into a scripted workflow: the account manager tells Switchy to create a contact group with the client's Slack webhook, spin up 5 uptime tests for their staging and production URLs, and add a PageSpeed test for their marketing site. The MCP handles all 11 tool types, so you can template the entire onboarding checklist. The boundary: if your agency runs 50+ active clients, you'll want StatusCake's bulk import API instead of conversational setup. For shops onboarding under 10 clients per quarter, this MCP is the faster path.
When this MCP fits quarterly performance reviews
A 5-person product team runs quarterly performance audits on their web app, checking uptime SLAs and PageSpeed scores across 12 customer-facing pages. The PM needs to pull all PageSpeed test results, compare them to last quarter's baseline, and identify which pages regressed. The StatusCake MCP works well here because it exposes the Get All PageSpeed Tests tool—Switchy can fetch the data, format it into a comparison table, and flag regressions without the PM opening StatusCake. The trade-off: this MCP doesn't write back PageSpeed test configs, so if you need to adjust test frequency or locations mid-audit, you're back in the dashboard. For teams running lightweight quarterly reviews with stable test configs, this MCP delivers the read-heavy workflow you need.
Frequently asked
What does the StatusCake MCP do in Switchy?
It lets your team query and manage StatusCake uptime monitors, PageSpeed tests, heartbeat checks, and contact groups directly from Switchy's AI workspace. You can list all tests, retrieve monitoring locations, delete outdated checks, and inspect contact group details without switching to the StatusCake dashboard. Useful for on-call engineers who need monitor context mid-incident or ops teams auditing test coverage.
Do I need admin access to connect StatusCake?
You need a StatusCake API key with read and write permissions. StatusCake issues keys at the account level, so whoever connects it in Switchy will grant the workspace access to all tests and contact groups under that account. If your team restricts API key creation to admins, you'll need their help to generate the credential during setup.
Can the MCP create new uptime tests or modify existing ones?
No. The current tool set covers listing tests, retrieving details, and deleting tests or contact groups, but it doesn't expose StatusCake's create or update endpoints. If you need to spin up a new monitor or change check intervals, you'll still open the StatusCake UI or hit their API directly outside Switchy.
Why use this instead of just logging into StatusCake?
Speed and context. When an alert fires, your team can ask Switchy "show me all failing tests" or "which contact group owns monitor X" without leaving the conversation. The MCP pulls live data, so you're not copy-pasting IDs or switching tabs. It's faster for triage; the StatusCake dashboard remains better for configuration work.
Who on the team should connect the StatusCake integration?
Whoever holds an API key with the permissions your team needs—typically an ops lead or platform engineer. Once connected, everyone in the Switchy workspace can query monitors and contact groups through the AI. The connection itself doesn't consume StatusCake plan seats, but the API key's scope determines what data the workspace can see.