# How to connect DocRaptor to OpenClaw (paste one key, 10 tools) > Connect DocRaptor to OpenClaw with ClawLink: paste your DocRaptor key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/docraptor The usual route to DocRaptor 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 DocRaptor setup: install one ClawHub skill, connect DocRaptor in the browser, and OpenClaw can call real DocRaptor 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 DocRaptor. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect DocRaptor** — 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 docraptor # connect DocRaptor (browser OAuth) npx -y @useclawlink/cli actions docraptor # list available actions npx -y @useclawlink/cli run docraptor --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 DocRaptor in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your DocRaptor API key once. Verify the connection by asking OpenClaw: > Create it in DocRaptor for me, then confirm the important fields before you finish. ### 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 DocRaptor is connected in the dashboard, that agent calls the same 10 DocRaptor 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). ## DocRaptor MCP for OpenClaw Looking for a DocRaptor MCP server for OpenClaw? ClawLink connects DocRaptor to OpenClaw and exposes 10 DocRaptor 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 DocRaptor integration](https://claw-link.dev/hermes/docraptor) works the same way. ## What the OpenClaw DocRaptor integration can do 10 DocRaptor tools are ready for OpenClaw once the account is connected. ### All 10 DocRaptor tools for OpenClaw | Tool | What it does | |---|---| | **Create doc** `docraptor_create_doc` | Create a PDF or Excel document synchronously from HTML content or URL | | **Create document from referrer** `docraptor_create_document_from_referrer` | Convert webpages into documents using referrer-based authentication without an API key | | **Get async doc** `docraptor_get_async_doc` | Download a completed asynchronous document using the download URL from status response | | **Get async doc status** `docraptor_get_async_doc_status` | Check the status of an asynchronously created document | | **List documents json** `docraptor_list_documents_json` | Retrieve a paginated list of previously created documents with metadata in JSON format | | **List documents xml** `docraptor_list_documents_xml` | Retrieve a paginated list of previously created documents with metadata in XML format | | **List ips json** `docraptor_list_ips_json` | Get list of IP addresses that DocRaptor uses to download assets | | **List ips text** `docraptor_list_ips_text` | Retrieve a list of IP addresses that DocRaptor uses to download assets in plain text format | | **Create async doc** `docraptor_create_async_doc` | Create documents asynchronously from HTML content | | **Create hosted async doc** `docraptor_create_hosted_async_doc` | Create a hosted document asynchronously | ## Example prompts **Create Doc** > Create it in DocRaptor for me, then confirm the important fields before you finish. **Create Document From Referrer** > Create it in DocRaptor for me, then confirm the important fields before you finish. **Get Async Doc** > Pull the relevant data from DocRaptor, summarize it in plain English, and point out anything that needs attention. **Get Async Doc Status** > Pull the relevant data from DocRaptor, 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 DocRaptor working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the DocRaptor API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected DocRaptor 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 DocRaptor. | 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 DocRaptor actions to the runtime in a format your agent can reliably use. | 10 tools for DocRaptor are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DocRaptor 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 DocRaptor in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the DocRaptor 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 DocRaptor skill but can't call the tools The ClawHub skill teaches OpenClaw about DocRaptor, but the calls run through the ClawLink plugin and your connected account. Make sure DocRaptor 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 DocRaptor 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 DocRaptor tools DocRaptor 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 DocRaptor 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. ### DocRaptor 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 DocRaptor has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw DocRaptor integration? Yes. ClawLink is the fastest way to connect OpenClaw to DocRaptor: link your DocRaptor account once in the browser and OpenClaw can call the DocRaptor API through 10 ready-made tools — no custom code or token handling. ### How do I add DocRaptor to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink DocRaptor skill from ClawHub, then you click Connect in the dashboard to authorize DocRaptor. OpenClaw calls the tools from the next message — no config files, and the DocRaptor key you paste is stored server-side instead of in your environment. ### How long does it take to connect DocRaptor to OpenClaw? About two minutes. Sign in, click Connect next to DocRaptor in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring DocRaptor 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 DocRaptor working from chat. ### OpenClaw installed the DocRaptor skill but can't call the tools The ClawHub skill teaches OpenClaw about DocRaptor, but the calls run through the ClawLink plugin and your connected account. Make sure DocRaptor 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 - [GitHub](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 - [SafetyCulture tools](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.