Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Search Raindrop.io bookmarks and review tag and collection plans. Read-only MCP by default.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
RAINDROP_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"raindrop-cli": {
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli",
"mcp",
"serve"
],
"env": {
"RAINDROP_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add raindrop-cli --env RAINDROP_TOKEN=your-value -- npx -y @machineyearn/raindrop-cli mcp serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"raindrop-cli": {
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli",
"mcp",
"serve"
],
"env": {
"RAINDROP_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"raindrop-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli",
"mcp",
"serve"
],
"env": {
"RAINDROP_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account KingPsychopath, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: RAINDROP_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 27 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Find, review and organize your saved links. Keep your tags. Bring your own AI.
Turn a growing Raindrop.io library into something easier to use. Search saved links, inspect collections, find cleanup opportunities and review suggestions before making changes. Use it from your terminal or let your favorite agent do the reading and planning.
A Raindrop.io CLI, MCP server and reviewed bookmark organizer from Machineyearn, built as an independent integration.
brew install machineyearningengineer/tap/rdrop
npm install --global @machineyearn/raindrop-cli@0.2.1 rdrop version
Prefer no global install? Use npx --yes @machineyearn/raindrop-cli@0.2.1 COMMAND. Native downloads cover macOS, Linux and Windows on Intel/AMD and ARM. Builds and checksums.
Create a token in your Raindrop integration settings. Add it to the private file ~/.config/rdrop/env:
RAINDROP_TOKEN=your_token_here
Give the directory permissions 700 and the file 600, then run rdrop doctor. Keep the token out of chat and Git. Setup and troubleshooting.
Copy this into Codex, Claude or your preferred coding agent. It can help with setup too:
Set up https://github.com/machineyearningengineer/raindrop-cli so you can help
manage my Raindrop library. Use its plugin/MCP when available, otherwise use the CLI. Check installation and authentication; have me add the token privately. Use the existing model and configured services first.
Start with a cleanup report and a small sample. Use my existing tags and collections. Choose useful tools for search, content, classification and planning; connect extra model providers, Executor or ACP only if needed. Show the exact proposed changes and a dry-run. Preserve my tags and notes, flag uncertain suggestions, and apply only the exact plan I approve.
Connect an agent, or start in your shell with rdrop collections --tree, rdrop search 'type:article #go' --json and rdrop cleanup report --json.
| You want to… | Start here |
|---|---|
| Find links, manage collections or export your library | Shell commands |
| Use Codex, Claude or another MCP client | Client setup and plugins |
| Ask a model to inspect your library and propose changes | Run a model directly |
| Use Raindrop's semantic search and AI-assisted reads | Official MCP tools |
| Classify selected bookmarks with Jev, Laya or Clef | Decision providers |
| Run portable Raindrop tools in Executor | Executor setup |
Begin with a report and select the exact bookmarks you want to review:
rdrop cleanup report --json > cleanup-report.json
rdrop context --ids 101,102 > library-context.json jq 'del(.snapshots)' library-context.json > model-context.json
The model view contains your existing tag names, collection paths and bookmark metadata. Keep the original context private: its snapshots are used to detect edits before applying. Ask any model or rule engine for the proposal format, then validate it:
rdrop organize plan --context library-context.json --proposal proposal.json > organization.json
jq '.plan // error("No accepted changes")' organization.json > reviewed-plan.json
rdrop cleanup apply reviewed-plan.json --dry-run rdrop cleanup apply reviewed-plan.json --yes
Plans keep existing tags and can combine new tags with a collection move. Unknown names and destinations fail validation; new tags need explicit naming rules. Account, digest and snapshots are checked before writing. Concurrent edits or partial failures need inspection and a fresh plan. Organizing and recovery.
The Codex and Claude plugin bundles a shared organizing skill and a read-only MCP connection. Install instructions also cover direct setup for other local clients.
rdrop connect mcp # client configuration, without tokens
rdrop mcp serve # read-only tools over stdio rdrop mcp tools --search 'organize tags' # discover relevant schemas offline rdrop mcp tools --name raindrop_context # inspect one exact schema rdrop mcp serve --official # also include Raindrop's hosted AI reads
Default tools read and plan. Enable writes only for an authorized host that enforces review. The official extension imports documented read tools; its plan limits and service availability still apply. Coverage and comparison with the official server.
You can also run a model directly:
# With your model API key in a private environment:
rdrop agent --model your-tool-capable-model --json \ 'Review the first page of untagged bookmarks. Use existing tags and propose a plan.' > agent-result.json
The model receives actual tool results and returns a response plus exact generated plans. Step, call and time limits bound the run. Local Chat Completions servers and hosted Responses APIs are supported. Jev, Laya and Cloudflare Clef provide typed category decisions; uncertainty stays visible. Model setup and exact commands.
A real Qwen/Laya loop classified bookmarks, generated a plan and applied it to a disposable test library while preserving existing tags and notes. The local Executor deployment passed connected-account health and live read checks. Repeat the verification, including its limits: this smoke check is not an accuracy benchmark, and Jev/Clef live inference requires provider credentials.
The product focuses on Raindrop. Model providers and proposal formats are agnostic; Obsidian and other note sources remain future options.
The public name is rdrop for Raindrop.io. Stable technical identifiers are the raindrop-cli repository, @machineyearn/raindrop-cli npm package, rdrop command and raindrop@machineyearn plugin. Storage support currently focuses on Raindrop.io; model and agent connections are provider-neutral.
A native Go CLI, local MCP server and direct model loop share the command implementation. The REST client, model clients and planning code use the standard library; MCP uses the official Go SDK. ACP configuration supplies this server to an existing ACP agent. Executor offers a smaller portable REST adapter. Docker is available as a packaging option.
make check # Go checks, build and generated-doc parity
make check-integrations # npm, Executor and Laya contracts make assets # regenerate the terminal graphic