# How to connect Context7 to OpenClaw (paste one key, 2 tools) > Connect Context7 to OpenClaw with ClawLink: paste your Context7 key once and 2 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/context7 The usual route to Context7 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 Context7 setup: install one ClawHub skill, connect Context7 in the browser, and OpenClaw can call real Context7 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 Context7. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Context7** — 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 context7 # connect Context7 (browser OAuth) npx -y @useclawlink/cli actions context7 # list available actions npx -y @useclawlink/cli run context7 --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 Context7 in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Context7 API key once. Verify the connection by asking OpenClaw: > Use Context7 to mcp query docs 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 Context7 is connected in the dashboard, that agent calls the same 2 Context7 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). ## Context7 MCP for OpenClaw Looking for a Context7 MCP server for OpenClaw? ClawLink connects Context7 to OpenClaw and exposes 2 Context7 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 Context7 integration](https://claw-link.dev/hermes/context7) works the same way. ## What the OpenClaw Context7 integration can do 2 Context7 tools are ready for OpenClaw once the account is connected. ### All 2 Context7 tools for OpenClaw | Tool | What it does | |---|---| | **Mcp query docs** `context7_mcp_query_docs` | Retrieves and queries up-to-date documentation and code examples from Context7 for any | | **Mcp resolve library ID** `context7_mcp_resolve_library_id` | Resolves a package/product name to a Context7-compatible library ID and returns matching | ## Example prompts **Mcp Query Docs** > Use Context7 to mcp query docs and walk me through the result in plain English. **Mcp Resolve Library Id** > Use Context7 to mcp resolve library id 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 Context7 working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Context7 API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Context7 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 Context7. | 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 Context7 actions to the runtime in a format your agent can reliably use. | 2 tools for Context7 are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Context7 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 Context7 in the browser, and the 2 tools above work from chat. There is no SDK and no config file, and the Context7 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 Context7 skill but can't call the tools The ClawHub skill teaches OpenClaw about Context7, but the calls run through the ClawLink plugin and your connected account. Make sure Context7 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 Context7 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 Context7 tools Context7 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 Context7 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. ### Context7 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 Context7 has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Context7 integration? Yes. ClawLink is the fastest way to connect OpenClaw to Context7: link your Context7 account once in the browser and OpenClaw can call the Context7 API through 2 ready-made tools — no custom code or token handling. ### How do I add Context7 to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Context7 skill from ClawHub, then you click Connect in the dashboard to authorize Context7. OpenClaw calls the tools from the next message — no config files, and the Context7 key you paste is stored server-side instead of in your environment. ### How long does it take to connect Context7 to OpenClaw? About two minutes. Sign in, click Connect next to Context7 in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Context7 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 Context7 working from chat. ### OpenClaw installed the Context7 skill but can't call the tools The ClawHub skill teaches OpenClaw about Context7, but the calls run through the ClawLink plugin and your connected account. Make sure Context7 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 GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.