How to connect Statuscake to OpenClaw
Connect Statuscake to OpenClaw with ClawLink: paste your Statuscake key once and 30 tools work from chat. No MCP server to run, nothing stored on your machine.
StatuscakeAPI KEYMCPStatusCake is a website monitoring platform that provides observability for applications, offering features like uptime monitoring, page speed monitoring, SSL monitoring, and more.. Once connected, OpenClaw can read and act on Statuscake from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Statuscake access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Statuscake setup: install one ClawHub skill, connect Statuscake in the browser, and OpenClaw can call real Statuscake actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Statuscake.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Statuscake
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Statuscake?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Statuscake in the ClawLink dashboard — paste your Statuscake API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Statuscake, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Statuscake is connected in the dashboard, that agent calls the same 30 Statuscake tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Statuscake MCP for OpenClaw
Looking for a Statuscake MCP server for OpenClaw? ClawLink connects Statuscake to OpenClaw and exposes 30 Statuscake tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Statuscake integration works the same way.
What the OpenClaw Statuscake integration can do
30 Statuscake tools are ready for OpenClaw once the account is connected. The 25 below are the ones people reach for most; your agent can call all 30.
25 of 30 Statuscake tools for OpenClaw
| Tool | What it does |
|---|---|
Get all contact groups statuscake_get_all_contact_groups | Retrieves a paginated list of contact groups for alert notifications |
Get all locations statuscake_get_all_locations | Retrieves all available uptime monitoring server locations from StatusCake |
Get all pagespeed tests statuscake_get_all_pagespeed_tests | Retrieve all PageSpeed tests |
Get all tests statuscake_get_all_tests | Retrieve a list of all tests |
Get contact group details statuscake_get_contact_group_details | Retrieve details of a specific contact group |
Get heartbeat checks statuscake_get_heartbeat_checks | List heartbeat checks |
Get heartbeat test statuscake_get_heartbeat_test | Retrieve details of a specific heartbeat check |
Get pagespeed test statuscake_get_pagespeed_test | Retrieve details of a specific pagespeed check |
Get ssl check details statuscake_get_ssl_check_details | Retrieve details of a specific SSL check |
Get ssl checks statuscake_get_ssl_checks | Retrieve a paginated list of SSL checks configured in your StatusCake account |
Get uptime test statuscake_get_uptime_test | Retrieve details of a specific uptime test |
List pagespeed monitoring locations statuscake_list_pagespeed_monitoring_locations | Retrieves all available PageSpeed monitoring server locations from StatusCake |
List pagespeed test history statuscake_list_pagespeed_test_history | Retrieve pagespeed check history for a given test ID |
List uptime test alerts statuscake_list_uptime_test_alerts | Retrieve a list of alerts for a specific uptime check |
List uptime test history statuscake_list_uptime_test_history | Retrieve uptime check history for a given test ID |
List uptime test periods statuscake_list_uptime_test_periods | Retrieve a list of uptime check periods for a specific test |
Create contact group statuscake_create_contact_group | Create a contact group for alert notifications in StatusCake |
Create heartbeat test statuscake_create_heartbeat_test | Create a heartbeat check in StatusCake |
Create pagespeed test statuscake_create_pagespeed_test | Create a new pagespeed check in StatusCake |
Create uptime test statuscake_create_uptime_test | Create a new uptime monitoring check in StatusCake |
Update contact group statuscake_update_contact_group | Updates an existing contact group's configuration in StatusCake |
Update heartbeat test statuscake_update_heartbeat_test | Update an existing heartbeat check with new parameters |
Update pagespeed test statuscake_update_pagespeed_test | Updates a pagespeed check with the given parameters |
Update ssl test statuscake_update_ssl_test | Update an SSL check with new configuration parameters |
Update uptime test statuscake_update_uptime_test | Updates an uptime check with the given parameters |
Try it: find the Statuscake tool you need
Browse the 25 Statuscake tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Statuscake, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Statuscake, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Statuscake, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Statuscake, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Statuscake working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Statuscake API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Statuscake account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Statuscake. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Statuscake actions to the runtime in a format your agent can reliably use. | 30 tools for Statuscake are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Statuscake to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Statuscake in the browser, and the 30 tools above work from chat. There is no SDK and no config file, and the Statuscake key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Statuscake skill but can't call the tools
The ClawHub skill teaches OpenClaw about Statuscake, but the calls run through the ClawLink plugin and your connected account. Make sure Statuscake is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Statuscake from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Statuscake tools
Statuscake tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Statuscake call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Statuscake returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Statuscake has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Statuscake integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Statuscake: link your Statuscake account once in the browser and OpenClaw can call the Statuscake API through 30 ready-made tools — no custom code or token handling.
How do I add Statuscake to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Statuscake skill from ClawHub, then you click Connect in the dashboard to authorize Statuscake. OpenClaw calls the tools from the next message — no config files, and the Statuscake key you paste is stored server-side instead of in your environment.
How long does it take to connect Statuscake to OpenClaw?
About two minutes. Sign in, click Connect next to Statuscake in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Statuscake up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Statuscake working from chat.
OpenClaw installed the Statuscake skill but can't call the tools
The ClawHub skill teaches OpenClaw about Statuscake, but the calls run through the ClawLink plugin and your connected account. Make sure Statuscake is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
Connect SafetyCulture
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.