# How to connect Serphouse to OpenClaw (paste one key, 18 tools) > Connect Serphouse to OpenClaw with ClawLink: paste your Serphouse key once and 18 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/serphouse The usual route to Serphouse 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 Serphouse setup: install one ClawHub skill, connect Serphouse in the browser, and OpenClaw can call real Serphouse 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 Serphouse. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Serphouse** — 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 serphouse # connect Serphouse (browser OAuth) npx -y @useclawlink/cli actions serphouse # list available actions npx -y @useclawlink/cli run serphouse --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 Serphouse in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Serphouse API key once. Verify the connection by asking OpenClaw: > Use Serphouse to account info 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 Serphouse is connected in the dashboard, that agent calls the same 18 Serphouse 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). ## Serphouse MCP for OpenClaw Looking for a Serphouse MCP server for OpenClaw? ClawLink connects Serphouse to OpenClaw and exposes 18 Serphouse 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 Serphouse integration](https://claw-link.dev/hermes/serphouse) works the same way. ## What the OpenClaw Serphouse integration can do 18 Serphouse tools are ready for OpenClaw once the account is connected. ### All 18 Serphouse tools for OpenClaw | Tool | What it does | |---|---| | **Account info** `serphouse_account_info` | Retrieve account information including active plan, credit usage, and account details | | **Domain list** `serphouse_domain_list` | Retrieve comprehensive list of search engine domains supported by the SERP API including | | **Google jobs search** `serphouse_google_jobs_search` | Perform real-time Google Jobs search to retrieve job listings | | **Language list** `serphouse_language_list` | Retrieve full list of languages supported by Google, Bing, and Yahoo for SERP requests | | **Location search** `serphouse_location_search` | Search and retrieve available locations for SERP API from Google or Bing geographical targeting | | **Serp check** `serphouse_serp_check` | Check the status of a previously submitted SERP task | | **Serp live get** `serphouse_serp_live_get` | Execute real-time search requests and retrieve search engine results immediately via HTTP GET | | **Serp live post** `serphouse_serp_live_post` | Execute real-time search requests and retrieve search engine results immediately using HTTP | | **Trends categories list** `serphouse_trends_categories_list` | Retrieve the full list of categories and subcategories for Google Trends searches | | **Trends check** `serphouse_trends_check` | Check the status of a previously submitted trend search task | | **Trends country list** `serphouse_trends_country_list` | Retrieve the full list of countries and states for Google Trends searches | | **Trends get** `serphouse_trends_get` | Retrieve the results of a completed trend search query | | **Trends language list** `serphouse_trends_language_list` | Retrieve the full list of supported languages for Google Trends searches | | **Trends search** `serphouse_trends_search` | Perform real-time Google Trends search to retrieve trend data for specified keywords | | **Trends timezone list** `serphouse_trends_timezone_list` | Retrieve full list of timezones and offset values for use in Google Trend search requests | | **Google serp advanced scheduled** `serphouse_google_serp_advanced_scheduled` | Schedule Google SERP scraping tasks that fetch up to 100 results by iterating through multiple | | **Serp schedule** `serphouse_serp_schedule` | Schedule SERP search tasks for asynchronous processing | | **Trends schedule** `serphouse_trends_schedule` | Schedule Google Trends search tasks with configuration for keywords, time ranges, and | ## Example prompts **Account Info** > Use Serphouse to account info and walk me through the result in plain English. **Domain List** > Use Serphouse to domain list and walk me through the result in plain English. **Google Jobs Search** > Search Serphouse for what I need, summarize the results, and tell me the next best action. **Language List** > Use Serphouse to language list 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 Serphouse working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Serphouse API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Serphouse 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 Serphouse. | 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 Serphouse actions to the runtime in a format your agent can reliably use. | 18 tools for Serphouse are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Serphouse 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 Serphouse in the browser, and the 18 tools above work from chat. There is no SDK and no config file, and the Serphouse 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 Serphouse skill but can't call the tools The ClawHub skill teaches OpenClaw about Serphouse, but the calls run through the ClawLink plugin and your connected account. Make sure Serphouse 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 Serphouse 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 Serphouse tools Serphouse 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 Serphouse 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. ### Serphouse 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 Serphouse has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Serphouse integration? Yes. ClawLink is the fastest way to connect OpenClaw to Serphouse: link your Serphouse account once in the browser and OpenClaw can call the Serphouse API through 18 ready-made tools — no custom code or token handling. ### How do I add Serphouse to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Serphouse skill from ClawHub, then you click Connect in the dashboard to authorize Serphouse. OpenClaw calls the tools from the next message — no config files, and the Serphouse key you paste is stored server-side instead of in your environment. ### How long does it take to connect Serphouse to OpenClaw? About two minutes. Sign in, click Connect next to Serphouse in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Serphouse 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 Serphouse working from chat. ### OpenClaw installed the Serphouse skill but can't call the tools The ClawHub skill teaches OpenClaw about Serphouse, but the calls run through the ClawLink plugin and your connected account. Make sure Serphouse 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 - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences