Busca marcadores de Raindrop.io, inspecciona colecciones y genera planes de organización mediante agentes de IA.
También conocido como KingPsychopath/raindrop-cli, raindrop-cli, @machineyearn/raindrop-cli
- Stars
- 2
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.2.1
- Último commit
- 3 nov 2026
- Licencia
- MIT
¿Qué es rdrop MCP?
rdrop es un MCP server. Busca marcadores de Raindrop.io, inspecciona colecciones y genera planes de organización mediante agentes de IA.
Resumen generado a partir del README del proyecto
Acerca del MCP server de rdrop
rdrop para Raindrop.io ofrece una forma de gestionar, buscar y organizar tu biblioteca de marcadores de Raindrop.io mediante herramientas de línea de comandos o agentes de IA. Funciona como un CLI nativo en Go y un MCP server que te permite inspeccionar colecciones, encontrar oportunidades de limpieza y generar planes de organización. Los usuarios pueden interactuar con sus datos a través de una terminal o conectando un cliente de IA como Claude o Codex para realizar tareas complejas de lectura y planificación.
Para usar este servidor, debes proporcionar un token de Raindrop almacenado en un archivo de configuración privado. El sistema está diseñado para ser neutral respecto al proveedor, lo que significa que puedes conectar modelos alojados o ejecutar opciones locales como Qwen y Laya. Prioriza la seguridad al permitirte revisar los cambios propuestos, como nuevas etiquetas o movimientos de colecciones, mediante un proceso de dry-run antes de que se aplique cualquier modificación real en tu cuenta. Esto garantiza que tus etiquetas y notas actuales permanezcan intactas durante el proceso de reorganización.
Qué puedes hacer con él
- 1Realizar auditorías de limpieza de la bibliotecaEjecuta un informe para identificar marcadores que necesiten atención o reorganización.
- 2Buscar y gestionar colecciones vía CLIUsa comandos de shell para buscar tipos específicos de enlaces o gestionar tu árbol de colecciones.
- 3Revisar cambios propuestos de forma seguraVerifica exactamente qué marcadores y etiquetas se modificarán antes de comprometerte con un plan de organización.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar rdrop MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar rdrop MCP en Claude Code
$ claude mcp add --env 'RAINDROP_TOKEN=<YOUR_RAINDROP_TOKEN>' raindrop-cli -- npx -y @machineyearn/raindrop-cliInstalar rdrop MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"raindrop-cli": {
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli"
],
"env": {
"RAINDROP_TOKEN": "<YOUR_RAINDROP_TOKEN>"
}
}
}
}Instalar rdrop MCP en VS Code
.vscode/mcp.json
{
"servers": {
"raindrop-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli"
],
"env": {
"RAINDROP_TOKEN": "<YOUR_RAINDROP_TOKEN>"
}
}
}
}Instalar rdrop MCP en VS Code CLI
$ code --add-mcp '{"name":"raindrop-cli","type":"stdio","command":"npx","args":["-y","@machineyearn/raindrop-cli"],"env":{"RAINDROP_TOKEN":"<YOUR_RAINDROP_TOKEN>"}}'Instalar rdrop MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"raindrop-cli": {
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli"
],
"env": {
"RAINDROP_TOKEN": "<YOUR_RAINDROP_TOKEN>"
}
}
}
}Instalar rdrop MCP en Codex
$ codex mcp add raindrop-cli --env 'RAINDROP_TOKEN=<YOUR_RAINDROP_TOKEN>' -- npx -y @machineyearn/raindrop-cliInstalar rdrop MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.raindrop-cli] command = "npx" args = ["-y", "@machineyearn/raindrop-cli"] [mcp_servers.raindrop-cli.env] RAINDROP_TOKEN = "<YOUR_RAINDROP_TOKEN>"
Instalar rdrop MCP en Gemini CLI
$ gemini mcp add -s user -e 'RAINDROP_TOKEN=<YOUR_RAINDROP_TOKEN>' raindrop-cli npx -- -y @machineyearn/raindrop-cliInstalar rdrop MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"raindrop-cli": {
"command": "npx",
"args": [
"-y",
"@machineyearn/raindrop-cli"
],
"env": {
"RAINDROP_TOKEN": "<YOUR_RAINDROP_TOKEN>"
}
}
}
}Configuración
RAINDROP_TOKENSecretoRaindrop.io API token. Alternatively configure the private rdrop env/token file; see setup.
| Nombre | Descripción | Tipo |
|---|---|---|
| RAINDROP_TOKEN | Raindrop.io API token. Alternatively configure the private rdrop env/token file; see setup. | Secreto |
Verificaciones automáticas
Ejecutado 13 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblekingpsychopath/raindrop-cli is public and reachablegithub.com/kingpsychopath/raindrop-cli ↗Aprobado
- El paquete indica este repositorio como su origen@machineyearn/raindrop-cli names kingpsychopath/raindrop-cli as sourcenpmjs.com/package/@machineyearn/raindrop-cli ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-03github.com/kingpsychopath/raindrop-cli ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @machineyearn/raindrop-cliAprobado
- No hay avisos críticos en el paquete ni en sus dependencias7 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubrdrop for Raindrop.io
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.
- Your organization stays yours. Start with the tags and collections you already created; preserve existing tags when applying a plan.
- Changes you can inspect. See exact bookmarks, proposed tags and destinations, then dry-run the plan before applying it.
- AI that fits your workflow. Connect Codex or Claude, use a hosted tool-capable model, or run local Qwen and Laya.
- A useful CLI without AI. Search, edit, export, manage highlights and collections, and build shell pipelines.
Get started
1. Install
brew install machineyearningengineer/tap/rdrop
# Or Node 22+, with optional dependencies enabled:
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.
2. Connect Raindrop
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.
3. Ask your agent
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.
Choose your workflow
| 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 |
Organize with a plan
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
# Review accepted changes, needsReview and unmentioned items.
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.
Use your agent
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.
Verified and maintained
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.
For developers
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
Preguntas sobre rdrop MCP
¿Cómo agrego rdrop MCP a Claude Code?
Ejecuta claude mcp add --env 'RAINDROP_TOKEN=<YOUR_RAINDROP_TOKEN>' raindrop-cli -- npx -y @machineyearn/raindrop-cli en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego rdrop MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Esta herramienta conserva mis etiquetas actuales?
Sí, la herramienta está diseñada para partir de tus etiquetas y colecciones existentes y conservarlas al aplicar un plan de organización.
¿Cómo puedo previsualizar los cambios antes de que se apliquen?
Puedes usar el flag dry-run al aplicar un plan de limpieza para ver los cambios propuestos sin ejecutarlos.