# How to connect Ragie to OpenClaw (paste one key, 31 tools) > Connect Ragie to OpenClaw with ClawLink: paste your Ragie key once and 31 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/ragie The usual route to Ragie 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 Ragie setup: install one ClawHub skill, connect Ragie in the browser, and OpenClaw can call real Ragie 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 Ragie. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Ragie** — 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 ragie # connect Ragie (browser OAuth) npx -y @useclawlink/cli actions ragie # list available actions npx -y @useclawlink/cli run ragie --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 Ragie in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Ragie API key once. Verify the connection by asking OpenClaw: > Create it in Ragie 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 Ragie is connected in the dashboard, that agent calls the same 31 Ragie 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). ## Ragie MCP for OpenClaw Looking for a Ragie MCP server for OpenClaw? ClawLink connects Ragie to OpenClaw and exposes 31 Ragie 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 Ragie integration](https://claw-link.dev/hermes/ragie) works the same way. ## What the OpenClaw Ragie integration can do 31 Ragie tools are ready for OpenClaw once the account is connected. The 28 below are the ones people reach for most; your agent can call all 31. ### 28 of 31 Ragie tools for OpenClaw | Tool | What it does | |---|---| | **Create oauth redirect URL** `ragie_create_oauth_redirect_url` | Create an OAuth redirect URL for initializing embedded connector OAuth flows | | **Get document** `ragie_get_document` | Retrieve a specific document by its unique identifier | | **Get document chunk** `ragie_get_document_chunk` | Retrieve a specific document chunk by its document and chunk ID | | **Get document chunk content** `ragie_get_document_chunk_content` | Retrieve document chunk content in requested format with streaming support for media | | **Get document chunks** `ragie_get_document_chunks` | Retrieve document chunks with pagination support | | **Get document content** `ragie_get_document_content` | Retrieve the content of a document by its ID | | **Get document summary** `ragie_get_document_summary` | Retrieve an LLM-generated summary of a document by its ID | | **Get partition** `ragie_get_partition` | Retrieve a partition by ID with usage statistics and resource limits | | **Get response** `ragie_get_response` | Retrieve a response by its unique identifier | | **List connection source types** `ragie_list_connection_source_types` | List available connection source types like 'google_drive' and 'notion' along with their | | **List connections connections get** `ragie_list_connections_connections_get` | List all connections sorted by creation date descending with pagination support | | **List documents** `ragie_list_documents` | List all documents sorted by creation date (descending) with pagination support | | **List entities by document** `ragie_list_entities_by_document` | Retrieve all extracted entities from a specific document with pagination support | | **List entities by instruction** `ragie_list_entities_by_instruction` | Retrieve entities generated by a specific instruction | | **List instructions** `ragie_list_instructions` | Retrieve all instruction records from the Ragie system | | **List partitions** `ragie_list_partitions` | Retrieve a paginated list of all partitions sorted by name in ascending order | | **Retrieve** `ragie_retrieve` | Retrieve relevant document chunks based on a query | | **Create document** `ragie_create_document` | Upload and process a document file in Ragie | | **Create document from URL** `ragie_create_document_from_url` | Ingest a document from a publicly accessible URL | | **Create document raw** `ragie_create_document_raw` | Ingest a document as raw text or JSON | | **Create instruction** `ragie_create_instruction` | Create a new instruction that applies natural language directives to documents as they're | | **Create partition partitions post** `ragie_create_partition_partitions_post` | Create a new partition for scoping documents and connections in Ragie | | **Patch document metadata** `ragie_patch_document_metadata` | Update metadata for a specific document with partial update support | | **Set partition limits** `ragie_set_partition_limits` | Set usage limits on partition pages and media | | **Update document from URL** `ragie_update_document_from_url` | Update an existing document by fetching content from a publicly accessible URL | | **Update document raw** `ragie_update_document_raw` | Update a document's content from raw text or JSON data | | **Update instruction** `ragie_update_instruction` | Update an instruction's active status | | **Update partition** `ragie_update_partition` | Update a partition's configuration including description, context-aware settings, and metadata | ## Example prompts **Create Oauth Redirect Url** > Create it in Ragie for me, then confirm the important fields before you finish. **Get Document** > Pull the relevant data from Ragie, summarize it in plain English, and point out anything that needs attention. **Get Document Chunk** > Pull the relevant data from Ragie, summarize it in plain English, and point out anything that needs attention. **Get Document Chunk Content** > Pull the relevant data from Ragie, 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 Ragie working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Ragie API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ragie 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 Ragie. | 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 Ragie actions to the runtime in a format your agent can reliably use. | 31 tools for Ragie are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Ragie 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 Ragie in the browser, and the 31 tools above work from chat. There is no SDK and no config file, and the Ragie 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 Ragie skill but can't call the tools The ClawHub skill teaches OpenClaw about Ragie, but the calls run through the ClawLink plugin and your connected account. Make sure Ragie 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 Ragie 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 Ragie tools Ragie 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 Ragie 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. ### Ragie 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 Ragie has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Ragie integration? Yes. ClawLink is the fastest way to connect OpenClaw to Ragie: link your Ragie account once in the browser and OpenClaw can call the Ragie API through 31 ready-made tools — no custom code or token handling. ### How do I add Ragie to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ragie skill from ClawHub, then you click Connect in the dashboard to authorize Ragie. OpenClaw calls the tools from the next message — no config files, and the Ragie key you paste is stored server-side instead of in your environment. ### How long does it take to connect Ragie to OpenClaw? About two minutes. Sign in, click Connect next to Ragie in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Ragie 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 Ragie working from chat. ### OpenClaw installed the Ragie skill but can't call the tools The ClawHub skill teaches OpenClaw about Ragie, but the calls run through the ClawLink plugin and your connected account. Make sure Ragie 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 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. - [OpenClaw Chatbotkit integration](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.