# How to connect Zenserp to OpenClaw (paste one key, 12 tools) > Connect Zenserp to OpenClaw with ClawLink: paste your Zenserp key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/zenserp The usual route to Zenserp 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 Zenserp setup: install one ClawHub skill, connect Zenserp in the browser, and OpenClaw can call real Zenserp 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 Zenserp. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Zenserp** — 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 zenserp # connect Zenserp (browser OAuth) npx -y @useclawlink/cli actions zenserp # list available actions npx -y @useclawlink/cli run zenserp --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 Zenserp in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Zenserp API key once. Verify the connection by asking OpenClaw: > Search Zenserp for what I need, summarize the results, and tell me the next best action. ### 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 Zenserp is connected in the dashboard, that agent calls the same 12 Zenserp 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). ## Zenserp MCP for OpenClaw Looking for a Zenserp MCP server for OpenClaw? ClawLink connects Zenserp to OpenClaw and exposes 12 Zenserp 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 Zenserp integration](https://claw-link.dev/hermes/zenserp) works the same way. ## What the OpenClaw Zenserp integration can do 12 Zenserp tools are ready for OpenClaw once the account is connected. ### All 12 Zenserp tools for OpenClaw | Tool | What it does | |---|---| | **Bing search** `zenserp_bing_search` | Obtain Bing search results | | **Get shopping product** `zenserp_get_shopping_product` | Retrieve detailed Google Shopping product page information by product_id | | **Get status** `zenserp_get_status` | Check the remaining API requests for your API key | | **Google reverse image search** `zenserp_google_reverse_image_search` | Perform a reverse image search on Google | | **Google search** `zenserp_google_search` | Perform a standard Google search via Zenserp | | **Google trends** `zenserp_google_trends` | Retrieve Google Trends data | | **List batches** `zenserp_list_batches` | List all submitted batches for your Zenserp API key | | **List countries** `zenserp_list_countries` | Get the list of supported Google country (gl) parameters | | **List languages** `zenserp_list_languages` | Get a list of supported Google interface language (hl) parameters | | **List locations** `zenserp_list_locations` | Get a list of supported geo locations for search targeting | | **List search engines** `zenserp_list_search_engines` | Get the list of supported search engines that can be queried via Zenserp | | **Yandex search** `zenserp_yandex_search` | Obtain Yandex search results via Zenserp API | ## Example prompts **Bing Search** > Search Zenserp for what I need, summarize the results, and tell me the next best action. **Get Shopping Product** > Pull the relevant data from Zenserp, summarize it in plain English, and point out anything that needs attention. **Get Status** > Pull the relevant data from Zenserp, summarize it in plain English, and point out anything that needs attention. **Google Reverse Image Search** > Search Zenserp for what I need, summarize the results, and tell me the next best action. ## 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 Zenserp working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Zenserp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Zenserp 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 Zenserp. | 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 Zenserp actions to the runtime in a format your agent can reliably use. | 12 tools for Zenserp are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Zenserp 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 Zenserp in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Zenserp 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 Zenserp skill but can't call the tools The ClawHub skill teaches OpenClaw about Zenserp, but the calls run through the ClawLink plugin and your connected account. Make sure Zenserp 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 Zenserp 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 Zenserp tools Zenserp 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 Zenserp 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. ### Zenserp 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 Zenserp has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Zenserp integration? Yes. ClawLink is the fastest way to connect OpenClaw to Zenserp: link your Zenserp account once in the browser and OpenClaw can call the Zenserp API through 12 ready-made tools — no custom code or token handling. ### How do I add Zenserp to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Zenserp skill from ClawHub, then you click Connect in the dashboard to authorize Zenserp. OpenClaw calls the tools from the next message — no config files, and the Zenserp key you paste is stored server-side instead of in your environment. ### How long does it take to connect Zenserp to OpenClaw? About two minutes. Sign in, click Connect next to Zenserp in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Zenserp 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 Zenserp working from chat. ### OpenClaw installed the Zenserp skill but can't call the tools The ClawHub skill teaches OpenClaw about Zenserp, but the calls run through the ClawLink plugin and your connected account. Make sure Zenserp 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 - [DataRobot](https://claw-link.dev/openclaw/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/openclaw/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.