Raindrop.io + Grok Bot
Connect Raindrop.io to Grok Bot
Prepare a grounded research brief
Read bookmarks with Grok Bot and Agent200. Prepare a research brief using the connected user’s own Raindrop.io account.
On this page
Overview
Identify the selected bookmark and ask Grok Bot to use the Agent200 connection. Inspect tool activity so browser context or another app does not replace the requested 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
- Grok Bot · 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.
- Grok Bot, with custom MCP servers allowed. Grok Bot comes with SuperGrok, Grok Business seats and paid Cursor plans. On a team, the admin's connector policy must allow the Agent200 server.
Connect Raindrop.io to Grok Bot
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Grok Bot in the next step, as "Authorization: Bearer <your key>". One key covers Raindrop.io and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open the custom connector form
In Grok Bot, open Connect apps from the sidebar and choose Add a custom connector at the bottom.
-
3
Step 3: Fill in the server and your key
Enter the name Agent200, pick Type Remote HTTPS, enter the server URL and add one HTTP header:
Authorizationwith the valueBearerfollowed by your key. Leave Client ID empty, then choose Add plugin.Add a custom connectorMCP: Grok Bot custom connector form Name: Agent200 Type: Remote HTTPS Server URL: https://api.agent200.com/mcp/ HTTP headers: Authorization: Bearer YOUR_AGENT200_API_KEY -
4
Step 4: Attach Agent200 in a chat
In a Bot chat, type
@and attach Agent200 to the task. Custom servers are account-wide, so every Bot on the account can use it. -
5
Step 5: Connect your Raindrop.io account
The first time you ask Grok Bot for something in Raindrop.io, Agent200 returns an authorization link. Open it and approve access on Raindrop.io's own page. Agent200 stores the connection and keeps it working; your password never reaches Grok Bot or Agent200.
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 Grok Bot.
Goal: connect Raindrop.io to Grok Bot with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/raindrop-io/framework/grok-bot/ 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 Grok Bot'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 Grok Bot: 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 Grok Bot'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/grok-bot.md
Raindrop.io tools Grok Bot 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 Grok Bot
In your own words, for something in Raindrop.io.
-
02
Grok Bot 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
Grok Bot 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.
