# How to connect Readwise Reader to OpenClaw (paste one key, 6 tools) > Connect Readwise Reader to OpenClaw with ClawLink: paste your Readwise Reader key once and 6 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/readwise-reader The usual route to Readwise Reader 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 Readwise Reader setup: install one ClawHub skill, connect Readwise Reader in the browser, and OpenClaw can call real Readwise Reader 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 Readwise Reader. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Readwise Reader** — 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 readwise-reader # connect Readwise Reader (browser OAuth) npx -y @useclawlink/cli actions readwise-reader # list available actions npx -y @useclawlink/cli run readwise-reader --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 Readwise Reader in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Readwise Reader API key once. Verify the connection by asking OpenClaw: > List the relevant items in Readwise Reader, group them by priority, and recommend what OpenClaw should do next. ### 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 Readwise Reader is connected in the dashboard, that agent calls the same 6 Readwise Reader 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). ## Readwise Reader MCP for OpenClaw Looking for a Readwise Reader MCP server for OpenClaw? ClawLink connects Readwise Reader to OpenClaw and exposes 6 Readwise Reader 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 Readwise Reader integration](https://claw-link.dev/hermes/readwise-reader) works the same way. ## What the OpenClaw Readwise Reader integration can do 6 Readwise Reader tools are ready for OpenClaw once the account is connected. The 5 below are the ones people reach for most; your agent can call all 6. ### 5 of 6 Readwise Reader tools for OpenClaw | Tool | What it does | |---|---| | **List documents** `readwise_reader_list_documents` | List, filter, incrementally sync, or fetch a specific Reader document | | **List tags** `readwise_reader_list_tags` | List tags in the connected Reader library, returning one page and a cursor for the next page | | **Bulk update documents** `readwise_reader_bulk_update_documents` | Partially update up to 50 Reader documents in one request and return a success or error result | | **Save document** `readwise_reader_save_document` | Save a URL or supplied HTML as a document in the connected Reader library, with optional | | **Update document** `readwise_reader_update_document` | Partially update supported fields on one Reader document by ID; omitted fields remain unchanged | ## Example prompts **List Documents** > List the relevant items in Readwise Reader, group them by priority, and recommend what OpenClaw should do next. **List Tags** > List the relevant items in Readwise Reader, group them by priority, and recommend what OpenClaw should do next. **Bulk Update Documents** > Use Readwise Reader to bulk update documents and walk me through the result in plain English. **Save Document** > Use Readwise Reader to save document 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 Readwise Reader working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Readwise Reader API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Readwise Reader 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 Readwise Reader. | 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 Readwise Reader actions to the runtime in a format your agent can reliably use. | 6 tools for Readwise Reader are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Readwise Reader 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 Readwise Reader in the browser, and the 6 tools above work from chat. There is no SDK and no config file, and the Readwise Reader 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 Readwise Reader skill but can't call the tools The ClawHub skill teaches OpenClaw about Readwise Reader, but the calls run through the ClawLink plugin and your connected account. Make sure Readwise Reader 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 Readwise Reader 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 Readwise Reader tools Readwise Reader 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 Readwise Reader 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. ### Readwise Reader 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 Readwise Reader has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Readwise Reader integration? Yes. ClawLink is the fastest way to connect OpenClaw to Readwise Reader: link your Readwise Reader account once in the browser and OpenClaw can call the Readwise Reader API through 6 ready-made tools — no custom code or token handling. ### How do I add Readwise Reader to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Readwise Reader skill from ClawHub, then you click Connect in the dashboard to authorize Readwise Reader. OpenClaw calls the tools from the next message — no config files, and the Readwise Reader key you paste is stored server-side instead of in your environment. ### How long does it take to connect Readwise Reader to OpenClaw? About two minutes. Sign in, click Connect next to Readwise Reader in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Readwise Reader 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 Readwise Reader working from chat. ### OpenClaw installed the Readwise Reader skill but can't call the tools The ClawHub skill teaches OpenClaw about Readwise Reader, but the calls run through the ClawLink plugin and your connected account. Make sure Readwise Reader 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 - [Trello](https://claw-link.dev/openclaw/trello) — Manage boards, lists, and cards - [OpenClaw Moco integration](https://claw-link.dev/openclaw/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints