Raindrop.io + OpenClaw
Connect Raindrop.io to OpenClaw
Prepare a grounded research brief
Read bookmarks with OpenClaw and Agent200. Prepare a research brief using the connected user’s own Raindrop.io account.
On this page
Overview
Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one bookmark the user can access. A saved setting alone does not verify the read.
Start with one identified bookmark. Preserve returned collection identity, bookmark title, URL, description, tags and other fields actually returned; report missing data and keep the workflow read-only.
Provider reference: Raindrop.io API.
- Connector
- Raindrop.io
- Works with
- OpenClaw · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Raindrop.io enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Raindrop.io account. They approve access once, on Raindrop.io's own page.
- OpenClaw, with custom MCP servers allowed. OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.
Connect Raindrop.io to OpenClaw
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
Step 2: Store your key in ~/.openclaw/.env
OpenClaw fills
${AGENT200_API_KEY}in its config from~/.openclaw/.env, so the key never sits in the config itself.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-http: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves${AGENT200_API_KEY}for OpenClaw. In the Control UI, add it under Settings > MCP, then put the header in the config editor on the same page.Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Authorize Raindrop.io
Connect the intended user and test one accessible bookmark.
Test your connection
Run one request to check everything is wired up.
Ask
Find the Raindrop.io collection I name and list relevant saved links. Prepare a concise research brief from returned bookmark titles, URLs, descriptions and tags. Identify the collection and disclose when the linked pages themselves were not read. Do not change bookmarks.
What should come back
- The selected bookmark is identified.
- Only returned collection identity, bookmark title, URL, description, tags and other fields actually returned are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the connected account, collection ID, search query and pagination. A bookmark record may lack a description or tag; report the gap without inventing page content.
Get your API key
Create a key in the Agent200 dashboard. It reaches Raindrop.io and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Raindrop.io to OpenClaw.
Goal: connect Raindrop.io to OpenClaw with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/raindrop-io/framework/openclaw/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into OpenClaw's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Raindrop.io is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to OpenClaw: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for OpenClaw's exact menus or commands. 4. The first Raindrop.io request returns an authorization link if the user has not connected Raindrop.io yet: show it to them and continue once they have approved access on Raindrop.io's own page. 5. Check it works with this request: "Find the Raindrop.io collection I name and list relevant saved links. Prepare a concise research brief from returned bookmark titles, URLs, descriptions and tags. Identify the collection and disclose when the linked pages themselves were not read. Do not change bookmarks." What should come back: - The selected bookmark is identified. - Only returned collection identity, bookmark title, URL, description, tags and other fields actually returned are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Raindrop.io, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/raindrop-io/framework/openclaw.md
Raindrop.io tools OpenClaw can call
-
List root collections
Readraindrop_io_list_collectionsFind the connected user’s top-level collections.
-
List child collections
Readraindrop_io_list_child_collectionsFind child collections under accessible collection folders.
-
Read a collection
Readraindrop_io_get_collectionRetrieve one identified collection and its returned metadata.
-
List bookmarks
Readraindrop_io_list_bookmarksRead saved links in one collection with the requested result scope.
-
Search bookmarks
Readraindrop_io_search_bookmarksSearch saved links in the connected user’s library.
-
Read a bookmark
Readraindrop_io_get_bookmarkRetrieve one identified saved link and its returned metadata.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in Raindrop.io.
-
02
OpenClaw picks a tool
It sees the Raindrop.io tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Raindrop.io connection, within the tools and scopes your project allows.
-
04
OpenClaw answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Raindrop.io account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Raindrop.io enforces what its API grants.
Troubleshooting
The source cannot be read
Check the connected account, collection ID, search query and pagination. A bookmark record may lack a description or tag; report the gap without inventing page content.
FAQ
How do I verify this result?
Compare the named bookmark and returned collection identity, bookmark title, URL, description, tags and other fields actually returned with the source. Treat missing information as missing, not as a fact.
