# How to connect PageVitals to OpenClaw (paste one key, 28 tools) > Connect PageVitals to OpenClaw with ClawLink: paste your PageVitals key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/page-vitals The usual route to PageVitals 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 PageVitals setup: install one ClawHub skill, connect PageVitals in the browser, and OpenClaw can call real PageVitals 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 PageVitals. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PageVitals** — 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 page-vitals # connect PageVitals (browser OAuth) npx -y @useclawlink/cli actions page-vitals # list available actions npx -y @useclawlink/cli run page-vitals --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 PageVitals in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PageVitals API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from PageVitals, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PageVitals is connected in the dashboard, that agent calls the same 28 PageVitals 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). ## PageVitals MCP for OpenClaw Looking for a PageVitals MCP server for OpenClaw? ClawLink connects PageVitals to OpenClaw and exposes 28 PageVitals 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 PageVitals integration](https://claw-link.dev/hermes/page-vitals) works the same way. ## What the OpenClaw PageVitals integration can do 28 PageVitals tools are ready for OpenClaw once the account is connected. The 24 below are the ones people reach for most; your agent can call all 28. ### 24 of 28 PageVitals tools for OpenClaw | Tool | What it does | |---|---| | **Get multistep test** `page_vitals_get_multistep_test` | Get one multistep test definition, including its configured steps | | **Get page metrics** `page_vitals_get_page_metrics` | Get the latest Lighthouse and Chrome UX metrics for one configured page and device | | **Get page opportunities** `page_vitals_get_page_opportunities` | List Lighthouse improvement opportunities for a page/device, or return the full variable-shape | | **Get page timeline** `page_vitals_get_page_timeline` | Get one historical timeline for a page/device: combined loading metrics, CrUX, network bytes | | **Get test** `page_vitals_get_test` | Get the detailed Lighthouse, timing, resource, budget, and validation summary for one synthetic | | **Get test report** `page_vitals_get_test_report` | Get one specialized synthetic-test report: keyed Lighthouse opportunities, the request | | **Get test series** `page_vitals_get_test_series` | Get one synthetic test series and its individual tests, statuses, page IDs, device variants | | **List budgets** `page_vitals_list_budgets` | List performance budgets, current status, notification settings, and affected pages for a | | **List configured pages** `page_vitals_list_configured_pages` | List the raw pages configured for PageVitals monitoring on a website | | **List multistep runs** `page_vitals_list_multistep_runs` | List historical runs for one multistep test, including status, duration, interaction | | **List multistep tests** `page_vitals_list_multistep_tests` | List multistep tests configured for a website with recent metrics, state, and success rates | | **List page metrics** `page_vitals_list_page_metrics` | List every configured page/device combination for a website with recent timeline and latest | | **List test series** `page_vitals_list_test_series` | List recent synthetic test series for a website, including status and failure counts | | **List website opportunities** `page_vitals_list_website_opportunities` | List Lighthouse improvement opportunities aggregated across a website and the affected pages | | **List websites** `page_vitals_list_websites` | List websites visible to the connected PageVitals API key | | **Add configured pages** `page_vitals_add_configured_pages` | Add one or more explicitly supplied pages to PageVitals monitoring for a website | | **Create budget** `page_vitals_create_budget` | Create a persistent PageVitals performance budget for a website | | **Create multistep test** `page_vitals_create_multistep_test` | Create an empty PageVitals multistep test definition with an explicit name and device profile | | **Create website** `page_vitals_create_website` | Add a domain to the PageVitals account and begin managing it | | **Run multistep tests** `page_vitals_run_multistep_tests` | Trigger exactly one named multistep test or intentionally fan out to every multistep test | | **Run test series** `page_vitals_run_test_series` | Trigger synthetic tests for selected page/device variants, or for every configured test when | | **Update budget** `page_vitals_update_budget` | Replace a PageVitals performance budget's complete metric threshold and device scope | | **Update configured page** `page_vitals_update_configured_page` | Update a configured PageVitals page's URL, display alias, or both | | **Update multistep test** `page_vitals_update_multistep_test` | Update a multistep test's alias and device | ## Example prompts **Get Multistep Test** > Pull the relevant data from PageVitals, summarize it in plain English, and point out anything that needs attention. **Get Page Metrics** > Pull the relevant data from PageVitals, summarize it in plain English, and point out anything that needs attention. **Get Page Opportunities** > Pull the relevant data from PageVitals, summarize it in plain English, and point out anything that needs attention. **Get Page Timeline** > Pull the relevant data from PageVitals, 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 PageVitals working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PageVitals API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PageVitals 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 PageVitals. | 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 PageVitals actions to the runtime in a format your agent can reliably use. | 28 tools for PageVitals are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PageVitals 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 PageVitals in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the PageVitals 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 PageVitals skill but can't call the tools The ClawHub skill teaches OpenClaw about PageVitals, but the calls run through the ClawLink plugin and your connected account. Make sure PageVitals 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 PageVitals 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 PageVitals tools PageVitals 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 PageVitals 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. ### PageVitals 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 PageVitals has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PageVitals integration? Yes. ClawLink is the fastest way to connect OpenClaw to PageVitals: link your PageVitals account once in the browser and OpenClaw can call the PageVitals API through 28 ready-made tools — no custom code or token handling. ### How do I add PageVitals to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PageVitals skill from ClawHub, then you click Connect in the dashboard to authorize PageVitals. OpenClaw calls the tools from the next message — no config files, and the PageVitals key you paste is stored server-side instead of in your environment. ### How long does it take to connect PageVitals to OpenClaw? About two minutes. Sign in, click Connect next to PageVitals in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PageVitals 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 PageVitals working from chat. ### OpenClaw installed the PageVitals skill but can't call the tools The ClawHub skill teaches OpenClaw about PageVitals, but the calls run through the ClawLink plugin and your connected account. Make sure PageVitals 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 - [PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.