Connect rdrop for Raindrop.io using the native rdrop executable or the pinned npm launcher from a local MCP client. The server starts read-only, reads the normal private CLI configuration, and keeps stdout reserved for MCP messages. New here? Follow three-step setup and the copyable agent prompt first.
The plugin displays as rdrop for Raindrop.io and keeps the stable installation identifier raindrop@machineyearn and skill command /raindrop:organize. This independent integration is maintained by Machineyearn.
The shared package in integrations/agent-plugin includes a portable Agent Plugins manifest, Codex/Claude compatibility manifests, a read-only MCP connection and one organizing skill. The skill teaches tool discovery, existing-tag preservation, bounded context, uncertainty review and exact-plan apply. It does not enable mutation tools or configure credentials.
For Codex:
codex plugin marketplace add machineyearningengineer/raindrop-cli --ref v0.2.1
codex plugin add raindrop@machineyearnSupported desktop versions also expose this marketplace in their plugin directory. Reload/start a new session after installation. Older clients can use the direct MCP configuration below. See OpenAI's plugin packaging guide.
For Claude Code, run these inside Claude:
/plugin marketplace add machineyearningengineer/raindrop-cli
/plugin install raindrop@machineyearn
Invoke /raindrop:organize or ask it to organize your Raindrop library. For local development, use claude --plugin-dir ./integrations/agent-plugin. The manifests and marketplace were checked with claude plugin validate; this is package validation, not proof of every client's UI workflow. See Claude's plugin reference.
The MCP command is pinned to @machineyearn/raindrop-cli@0.2.1. Updating the plugin does not automatically authorize writes. Keep Node 22+ and optional npm dependencies enabled. Configure the token through the private CLI env/token file and run rdrop doctor before starting the client.
The source metadata uses io.github.machineyearningengineer/raindrop-cli for the next MCP Registry publication, displayed as rdrop for Raindrop.io. The published v0.2.1 listing remains io.github.KingPsychopath/raindrop-cli; changing GitHub usernames does not republish that listing or the npm package. It describes the pinned npm command, mcp serve arguments and private token setup. Registry discovery is separate from a client's plugin directory and does not provision an account or enable writes. Registry metadata and publishing.
For clients using mcpServers, including Claude Desktop and Cursor, add:
{
"mcpServers": {
"raindrop": {
"command": "npx",
"args": ["--yes", "@machineyearn/raindrop-cli@0.2.1", "mcp", "serve"]
}
}
}Or rdrop connect mcp --command /absolute/path/rdrop prints native configuration. GUI apps need an executable they can find; use an absolute command path when their PATH differs from your terminal. Leave tokens out of project configuration. A client running inside a container/remote workspace uses that environment's private token configuration.
| Client | Connection |
|---|---|
| Codex | Plugin above, or a local stdio MCP server |
| Claude Code / Claude Desktop | Plugin or local stdio server |
| Cursor / Windsurf | Add the stdio server in that client's MCP settings |
| VS Code / Copilot | Use its servers configuration with type: "stdio" and the same command/args |
| Zed / other local MCP hosts | Use their native stdio configuration format with the same command/args |
| Claude web/mobile, ChatGPT web and other remote-only hosts | Require a reachable HTTP MCP service; the local stdio command cannot serve this role |
These are transport-compatible setup routes, not a claim that every listed client has been independently tested here or that Raindrop lists this project as an official integration. See the official supported-client page for Raindrop's hosted HTTP/OAuth service.
Add --official to the local server's arguments to include Raindrop's official AI read tools. The client remains local stdio; the server makes an authenticated outbound connection to the official hosted service. Free/Pro limitations still apply.
rdrop connect acp supplies the local MCP server to an existing ACP agent. connect raindrop prints HTTP configuration for the official service; connect executor prints configuration for your Executor host. These are different connections with their own auth. Integration details.