# How to connect Raindrop.io to OpenClaw (paste one key, 11 tools)

> Connect Raindrop.io to OpenClaw with ClawLink: paste your Raindrop.io 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/raindrop

The usual route to Raindrop.io 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 Raindrop.io setup: install one ClawHub skill, connect Raindrop.io in the browser, and OpenClaw can call real Raindrop.io 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 Raindrop.io.

1. **Install ClawLink** — add the plugin to OpenClaw once.
2. **Connect Raindrop.io** — 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 raindrop  # connect Raindrop.io (browser OAuth)
npx -y @useclawlink/cli actions raindrop  # list available actions
npx -y @useclawlink/cli run raindrop <action> --input '<json>'  # 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 Raindrop.io in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Raindrop.io API key once.

Verify the connection by asking OpenClaw:

> Pull the relevant data from Raindrop.io, summarize it in plain English, and point out anything that needs attention.

### 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 Raindrop.io is connected in the dashboard, that agent calls the same 11 Raindrop.io 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).

## Raindrop.io MCP for OpenClaw

Looking for a Raindrop.io MCP server for OpenClaw? ClawLink connects Raindrop.io to OpenClaw and exposes 11 Raindrop.io 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 Raindrop.io integration](https://claw-link.dev/hermes/raindrop) works the same way.

## What the OpenClaw Raindrop.io integration can do

11 Raindrop.io tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 11.

### 9 of 11 Raindrop.io tools for OpenClaw

| Tool | What it does |
|---|---|
| **Get bookmark** `raindrop_get_bookmark` | Get one bookmark and its highlights by Raindrop ID |
| **List bookmarks** `raindrop_list_bookmarks` | List, search, filter, and sort bookmarks in a collection, all bookmarks, Unsorted, or Trash |
| **List collections** `raindrop_list_collections` | List all root and nested collections in the connected Raindrop account, including IDs, parent |
| **List tags** `raindrop_list_tags` | List tag names and bookmark counts globally or within one collection |
| **Create bookmark** `raindrop_create_bookmark` | Save one URL as a Raindrop bookmark with optional organization and notes |
| **Create bookmarks** `raindrop_create_bookmarks` | Create 1 to 100 bookmarks in one request with optional organization and notes |
| **Create collection** `raindrop_create_collection` | Create a root or nested Raindrop collection |
| **Update bookmark** `raindrop_update_bookmark` | Update selected bookmark fields, move it to another collection, or replace its tags while |
| **Update collection** `raindrop_update_collection` | Change selected properties of an existing Raindrop collection without replacing omitted |

## Example prompts

**Get Bookmark**

> Pull the relevant data from Raindrop.io, summarize it in plain English, and point out anything that needs attention.

**List Bookmarks**

> List the relevant items in Raindrop.io, group them by priority, and recommend what OpenClaw should do next.

**List Collections**

> List the relevant items in Raindrop.io, group them by priority, and recommend what OpenClaw should do next.

**List Tags**

> List the relevant items in Raindrop.io, group them by priority, and recommend what OpenClaw should do next.

## 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 Raindrop.io working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Raindrop.io API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Raindrop.io 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 Raindrop.io. | 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 Raindrop.io actions to the runtime in a format your agent can reliably use. | 11 tools for Raindrop.io are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Raindrop.io 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 Raindrop.io in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Raindrop.io 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 Raindrop.io skill but can't call the tools
The ClawHub skill teaches OpenClaw about Raindrop.io, but the calls run through the ClawLink plugin and your connected account. Make sure Raindrop.io 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 Raindrop.io 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 Raindrop.io tools
Raindrop.io 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 Raindrop.io 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.

### Raindrop.io 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 Raindrop.io has the right scopes or account access. A valid key can still be too limited for some reads or writes.

### Is there a OpenClaw Raindrop.io integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Raindrop.io: link your Raindrop.io account once in the browser and OpenClaw can call the Raindrop.io API through 11 ready-made tools — no custom code or token handling.

### How do I add Raindrop.io to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Raindrop.io skill from ClawHub, then you click Connect in the dashboard to authorize Raindrop.io. OpenClaw calls the tools from the next message — no config files, and the Raindrop.io key you paste is stored server-side instead of in your environment.

### How long does it take to connect Raindrop.io to OpenClaw?
About two minutes. Sign in, click Connect next to Raindrop.io in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

### Why use ClawLink instead of wiring Raindrop.io 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 Raindrop.io working from chat.

### OpenClaw installed the Raindrop.io skill but can't call the tools
The ClawHub skill teaches OpenClaw about Raindrop.io, but the calls run through the ClawLink plugin and your connected account. Make sure Raindrop.io 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 tools](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.
- [OpenClaw ClickUp integration](https://claw-link.dev/openclaw/clickup) — Manage tasks, docs, goals, and sprints
