# How to connect Context.dev to OpenClaw (paste one key, 11 tools) > Connect Context.dev to OpenClaw with ClawLink: paste your Context.dev key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/context-dev The usual route to Context.dev 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 Context.dev setup: install one ClawHub skill, connect Context.dev in the browser, and OpenClaw can call real Context.dev 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 Context.dev. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Context.dev** — 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 context-dev # connect Context.dev (browser OAuth) npx -y @useclawlink/cli actions context-dev # list available actions npx -y @useclawlink/cli run context-dev --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 Context.dev in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Context.dev API key once. Verify the connection by asking OpenClaw: > Use Context.dev to extract structured web data 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 Context.dev is connected in the dashboard, that agent calls the same 11 Context.dev 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). ## Context.dev MCP for OpenClaw Looking for a Context.dev MCP server for OpenClaw? ClawLink connects Context.dev to OpenClaw and exposes 11 Context.dev 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 Context.dev integration](https://claw-link.dev/hermes/context-dev) works the same way. ## What the OpenClaw Context.dev integration can do 11 Context.dev tools are ready for OpenClaw once the account is connected. ### All 11 Context.dev tools for OpenClaw | Tool | What it does | |---|---| | **Extract structured web data** `context_dev_extract_structured_web_data` | Crawl relevant pages from a website and return data matching a caller-provided JSON Schema and | | **Get brand** `context_dev_get_brand` | Retrieve enriched brand identity, logos, colors, industry, and description using exactly one | | **Get monitor limits** `context_dev_get_monitor_limits` | Return the connected account's plan and current monitor usage versus its monitor limit | | **Get webdb usage** `context_dev_get_webdb_usage` | Return WebDB credit balance, period consumption, row count, storage, and per-collection usage | | **Get website styleguide** `context_dev_get_website_styleguide` | Extract a website's colors, typography, spacing, shadows, font assets, and common component | | **List batches** `context_dev_list_batches` | List and filter the connected account's asynchronous web batches from newest to oldest | | **List monitors** `context_dev_list_monitors` | List and filter the connected organization's web monitors, returning one cursor-controlled page | | **List webdb collections** `context_dev_list_webdb_collections` | List the connected account's WebDB collections and return one cursor-controlled page, including | | **Parse file** `context_dev_parse_file` | Convert an uploaded document, image, source file, or data file into LLM-usable Markdown | | **Scrape webpage markdown** `context_dev_scrape_webpage_markdown` | Render one public URL and return its main or CSS-selected content as Markdown | | **Search brands** `context_dev_search_brands` | Prefix-search Context.dev's existing brand index by company name or domain and return up to 10 | ## Example prompts **Extract Structured Web Data** > Use Context.dev to extract structured web data and walk me through the result in plain English. **Get Brand** > Pull the relevant data from Context.dev, summarize it in plain English, and point out anything that needs attention. **Get Monitor Limits** > Pull the relevant data from Context.dev, summarize it in plain English, and point out anything that needs attention. **Get Webdb Usage** > Pull the relevant data from Context.dev, 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 Context.dev working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Context.dev API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Context.dev 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 Context.dev. | 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 Context.dev actions to the runtime in a format your agent can reliably use. | 11 tools for Context.dev are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Context.dev 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 Context.dev in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Context.dev 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 Context.dev skill but can't call the tools The ClawHub skill teaches OpenClaw about Context.dev, but the calls run through the ClawLink plugin and your connected account. Make sure Context.dev 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 Context.dev 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 Context.dev tools Context.dev 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 Context.dev 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. ### Context.dev 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 Context.dev has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Context.dev integration? Yes. ClawLink is the fastest way to connect OpenClaw to Context.dev: link your Context.dev account once in the browser and OpenClaw can call the Context.dev API through 11 ready-made tools — no custom code or token handling. ### How do I add Context.dev to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Context.dev skill from ClawHub, then you click Connect in the dashboard to authorize Context.dev. OpenClaw calls the tools from the next message — no config files, and the Context.dev key you paste is stored server-side instead of in your environment. ### How long does it take to connect Context.dev to OpenClaw? About two minutes. Sign in, click Connect next to Context.dev in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Context.dev 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 Context.dev working from chat. ### OpenClaw installed the Context.dev skill but can't call the tools The ClawHub skill teaches OpenClaw about Context.dev, but the calls run through the ClawLink plugin and your connected account. Make sure Context.dev 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](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. - [OpenClaw Just One API integration](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.