ClawLink

How to connect GTmetrix to OpenClaw

Connect GTmetrix to OpenClaw with ClawLink: paste your GTmetrix key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
GTmetrix
GTmetrix
GTmetrixAPI KEYMCP

GTmetrix is a performance testing and monitoring tool that analyzes website speed, provides detailed performance reports, and helps optimize web applications for better user experience.. Once connected, OpenClaw can read and act on GTmetrix from chat — pairing, token refresh, and tool wiring handled for you.

20 tools

The usual route to GTmetrix 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 GTmetrix setup: install one ClawHub skill, connect GTmetrix in the browser, and OpenClaw can call real GTmetrix 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 GTmetrix.

  1. 1

    Install 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. 2

    Connect GTmetrix

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with GTmetrix?"

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-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 GTmetrix in the ClawLink dashboard — paste your GTmetrix API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from GTmetrix, 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 login

login opens the same browser approval and stores a credential locally. Once GTmetrix is connected in the dashboard, that agent calls the same 20 GTmetrix tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

GTmetrix MCP for OpenClaw

Looking for a GTmetrix MCP server for OpenClaw? ClawLink connects GTmetrix to OpenClaw and exposes 20 GTmetrix tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes GTmetrix integration works the same way.

What the OpenClaw GTmetrix integration can do

20 GTmetrix tools are ready for OpenClaw once the account is connected. The 18 below are the ones people reach for most; your agent can call all 20.

18 of 20 GTmetrix tools for OpenClaw

ToolWhat it does
Get browser gtmetrix_get_browserRetrieve browser details from GTmetrix
Get browsers gtmetrix_get_browsersRetrieve the list of available browsers for GTmetrix performance tests
Get location gtmetrix_get_locationRetrieve location details from GTmetrix
Get locations gtmetrix_get_locationsRetrieve the list of available GTmetrix test locations
Get page gtmetrix_get_pageRetrieve page details from the user's GTmetrix account
Get page latest report gtmetrix_get_page_latest_reportRetrieve the most recent test report for a monitored page in GTmetrix
Get page reports gtmetrix_get_page_reportsRetrieve the report list associated with a monitored page in GTmetrix
Get pages gtmetrix_get_pagesRetrieve the page list from your GTmetrix account
Get report gtmetrix_get_reportRetrieve a GTmetrix test report by its identifier
Get report resource gtmetrix_get_report_resourceGet a report resource such as screenshot, HAR file, video, PDF, or Lighthouse JSON
Get simulated device gtmetrix_get_simulated_deviceRetrieve simulated device details
Get simulated devices gtmetrix_get_simulated_devicesRetrieve the list of simulated devices available in GTmetrix
Get status gtmetrix_get_statusRetrieve the current API account state and remaining credits
Get test gtmetrix_get_testRetrieve test details for a specific GTMetrix test
Get tests gtmetrix_get_testsRetrieve the test list from your GTmetrix account with pagination and filtering support
Retest page gtmetrix_retest_pageInitiate a retest of a GTmetrix page with same parameters
Retest report gtmetrix_retest_reportInitiate a retest of a completed GTmetrix report with same parameters
Start test gtmetrix_start_testStart a new GTmetrix test for a specified URL

Try it: find the GTmetrix tool you need

Browse the 18 GTmetrix 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 GTmetrix, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from GTmetrix, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from GTmetrix, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from GTmetrix, summarize it in plain English, and point out anything that needs attention.

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 GTmetrix working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the GTmetrix API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected GTmetrix account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for GTmetrix.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right GTmetrix actions to the runtime in a format your agent can reliably use.20 tools for GTmetrix are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes GTmetrix 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 GTmetrix in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the GTmetrix 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 GTmetrix skill but can't call the tools

The ClawHub skill teaches OpenClaw about GTmetrix, but the calls run through the ClawLink plugin and your connected account. Make sure GTmetrix 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 GTmetrix 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 GTmetrix tools

GTmetrix 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 GTmetrix 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.

GTmetrix 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 GTmetrix 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 GTmetrix integration?

Yes. ClawLink is the fastest way to connect OpenClaw to GTmetrix: link your GTmetrix account once in the browser and OpenClaw can call the GTmetrix API through 20 ready-made tools — no custom code or token handling.

How do I add GTmetrix to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink GTmetrix skill from ClawHub, then you click Connect in the dashboard to authorize GTmetrix. OpenClaw calls the tools from the next message — no config files, and the GTmetrix key you paste is stored server-side instead of in your environment.

How long does it take to connect GTmetrix to OpenClaw?

About two minutes. Sign in, click Connect next to GTmetrix in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring GTmetrix 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 GTmetrix working from chat.

OpenClaw installed the GTmetrix skill but can't call the tools

The ClawHub skill teaches OpenClaw about GTmetrix, but the calls run through the ClawLink plugin and your connected account. Make sure GTmetrix 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.