# How to connect Keyword to OpenClaw (paste one key, 20 tools) > Connect Keyword to OpenClaw with ClawLink: paste your Keyword key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/keyword The usual route to Keyword 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 Keyword setup: install one ClawHub skill, connect Keyword in the browser, and OpenClaw can call real Keyword 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 Keyword. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Keyword** — 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 keyword # connect Keyword (browser OAuth) npx -y @useclawlink/cli actions keyword # list available actions npx -y @useclawlink/cli run keyword --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 Keyword in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Keyword API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Keyword, 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 Keyword is connected in the dashboard, that agent calls the same 20 Keyword 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). ## Keyword MCP for OpenClaw Looking for a Keyword MCP server for OpenClaw? ClawLink connects Keyword to OpenClaw and exposes 20 Keyword 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 Keyword integration](https://claw-link.dev/hermes/keyword) works the same way. ## What the OpenClaw Keyword integration can do 20 Keyword tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 20. ### 17 of 20 Keyword tools for OpenClaw | Tool | What it does | |---|---| | **Get current user** `keyword_get_current_user` | Retrieve the current authenticated user's account information | | **Get keyword** `keyword_get_keyword` | Retrieve all keyword settings and ranking metrics for a single keyword | | **Get project** `keyword_get_project` | Retrieve a single project's summary from Keyword.com | | **Get project metrics** `keyword_get_project_metrics` | Retrieve keyword movement metrics for a project, group, or tag | | **Get ranking history** `keyword_get_ranking_history` | Retrieve Google ranking history for specified keywords for up to 180 days | | **Get sov history** `keyword_get_sov_history` | Retrieve Share of Voice data over time for a specific project | | **Get top pages** `keyword_get_top_pages` | Retrieve Top Pages data for a project showing ranking URLs with keyword counts, average rank | | **List active projects** `keyword_list_active_projects` | Retrieve all active projects with their groups, tags, and keyword counts | | **List alerts** `keyword_list_alerts` | Retrieve all alerts for the Keyword.com account with pagination and sorting options | | **List keywords** `keyword_list_keywords` | Retrieve all keywords and their ranking data in a project or group | | **List project regions** `keyword_list_project_regions` | List all Google regions being tracked in a Keyword.com project | | **Add keywords** `keyword_add_keywords` | Add keywords to a Keyword.com project for search ranking tracking | | **Archive project** `keyword_archive_project` | Archive a project in Keyword.com | | **Create project** `keyword_create_project` | Create a new project or group in Keyword.com account | | **Refresh keywords** `keyword_refresh_keywords` | Trigger an on-demand update for all keywords in one or more projects or groups | | **Restore project** `keyword_restore_project` | Restore an archived project or group | | **Update keywords** `keyword_update_keywords` | Update keyword settings in a project | ## Example prompts **Get Current User** > Pull the relevant data from Keyword, summarize it in plain English, and point out anything that needs attention. **Get Keyword** > Pull the relevant data from Keyword, summarize it in plain English, and point out anything that needs attention. **Get Project** > Pull the relevant data from Keyword, summarize it in plain English, and point out anything that needs attention. **Get Project Metrics** > Pull the relevant data from Keyword, 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 Keyword working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Keyword API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Keyword 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 Keyword. | 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 Keyword actions to the runtime in a format your agent can reliably use. | 20 tools for Keyword are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Keyword 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 Keyword in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Keyword 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 Keyword skill but can't call the tools The ClawHub skill teaches OpenClaw about Keyword, but the calls run through the ClawLink plugin and your connected account. Make sure Keyword 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 Keyword 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 Keyword tools Keyword 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 Keyword 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. ### Keyword 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 Keyword has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Keyword integration? Yes. ClawLink is the fastest way to connect OpenClaw to Keyword: link your Keyword account once in the browser and OpenClaw can call the Keyword API through 20 ready-made tools — no custom code or token handling. ### How do I add Keyword to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Keyword skill from ClawHub, then you click Connect in the dashboard to authorize Keyword. OpenClaw calls the tools from the next message — no config files, and the Keyword key you paste is stored server-side instead of in your environment. ### How long does it take to connect Keyword to OpenClaw? About two minutes. Sign in, click Connect next to Keyword in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Keyword 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 Keyword working from chat. ### OpenClaw installed the Keyword skill but can't call the tools The ClawHub skill teaches OpenClaw about Keyword, but the calls run through the ClawLink plugin and your connected account. Make sure Keyword 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 ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Connect 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. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences