# How to connect Visualping to OpenClaw (paste one key, 9 tools) > Connect Visualping to OpenClaw with ClawLink: paste your Visualping key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/visualping The usual route to Visualping 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 Visualping setup: install one ClawHub skill, connect Visualping in the browser, and OpenClaw can call real Visualping 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 Visualping. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Visualping** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect visualping # connect Visualping (browser OAuth) npx -y @useclawlink/cli actions visualping # list available actions npx -y @useclawlink/cli run visualping --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Visualping in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Visualping API key once. Verify the connection by asking OpenClaw: > Use Visualping to describe account and walk me through the result in plain English. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Visualping is connected in the dashboard, that agent calls the same 9 Visualping tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Visualping MCP for OpenClaw Looking for a Visualping MCP server for OpenClaw? ClawLink connects Visualping to OpenClaw and exposes 9 Visualping tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Visualping integration](https://claw-link.dev/hermes/visualping) works the same way. ## What the OpenClaw Visualping integration can do 9 Visualping tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9. ### 8 of 9 Visualping tools for OpenClaw | Tool | What it does | |---|---| | **Describe account** `visualping_describe_account` | Return the connected Visualping account, organization, workspaces, plan limits, balances, and | | **Get monitor** `visualping_get_monitor` | Get a monitor's configuration, check history, and detected changes in one response | | **List monitors** `visualping_list_monitors` | List and filter monitors visible to the connected workspace, returning one page and a | | **Preflight monitor checks** `visualping_preflight_monitor_checks` | Estimate the credits required to check one or more active monitors without launching a check or | | **Bulk create monitors** `visualping_bulk_create_monitors` | Create two or more active monitors with shared detection settings | | **Create monitor** `visualping_create_monitor` | Create a monitor in a workspace | | **Update monitor** `visualping_update_monitor` | Partially update a monitor's core URL, schedule, detection, state, or notification settings | | **Launch monitor checks** `visualping_launch_monitor_checks` | Immediately launch checks for one or more active monitors, consuming or reserving monitoring | ## Example prompts **Describe Account** > Use Visualping to describe account and walk me through the result in plain English. **Get Monitor** > Pull the relevant data from Visualping, summarize it in plain English, and point out anything that needs attention. **List Monitors** > List the relevant items in Visualping, group them by priority, and recommend what OpenClaw should do next. **Preflight Monitor Checks** > Use Visualping to preflight monitor checks and walk me through the result in plain English. ## 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 Visualping working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Visualping API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Visualping 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 Visualping. | 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 Visualping actions to the runtime in a format your agent can reliably use. | 9 tools for Visualping are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Visualping 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 Visualping in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Visualping key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Visualping skill but can't call the tools The ClawHub skill teaches OpenClaw about Visualping, but the calls run through the ClawLink plugin and your connected account. Make sure Visualping 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 Visualping 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 Visualping tools Visualping 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 Visualping 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. ### Visualping 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 Visualping has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Visualping integration? Yes. ClawLink is the fastest way to connect OpenClaw to Visualping: link your Visualping account once in the browser and OpenClaw can call the Visualping API through 9 ready-made tools — no custom code or token handling. ### How do I add Visualping to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Visualping skill from ClawHub, then you click Connect in the dashboard to authorize Visualping. OpenClaw calls the tools from the next message — no config files, and the Visualping key you paste is stored server-side instead of in your environment. ### How long does it take to connect Visualping to OpenClaw? About two minutes. Sign in, click Connect next to Visualping in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Visualping 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 Visualping working from chat. ### OpenClaw installed the Visualping skill but can't call the tools The ClawHub skill teaches OpenClaw about Visualping, but the calls run through the ClawLink plugin and your connected account. Make sure Visualping 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 - [Connect Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [Connect Moco](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints