raindrop-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAINDROP_TOKEN | Yes | Your Raindrop.io API token. Get it from https://app.raindrop.io/settings/integrations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_raindropA | Get a single bookmark by ID. |
| get_raindropsA | Get bookmarks from a collection with optional search and filtering. collectionId: 0=all, -1=unsorted, -99=trash. |
| create_raindropC | Create a new bookmark. |
| update_raindropB | Update an existing bookmark by ID. |
| delete_raindropA | Delete a bookmark by ID. Moves to trash, or permanently deletes if already in trash. |
| get_collectionsA | Get root-level collections. Set include_children=true to also return nested collections. |
| get_collectionA | Get a specific collection by ID. |
| create_collectionC | Create a new collection. |
| update_collectionC | Update an existing collection. |
| delete_collectionB | Delete a collection by ID. |
| get_tagsA | Get all tags, optionally filtered by collection. |
| rename_tagB | Rename a tag across all or a specific collection. |
| merge_tagsC | Merge multiple tags into one. |
| delete_tagsB | Delete one or more tags. |
| get_userA | Get current user information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool targets a distinct resource (collection, raindrop, tag, user) and action (get, create, update, delete, merge, rename). Singular/plural forms differentiate single vs. batch operations clearly, so there is no ambiguity between tools.
All tools follow a consistent verb_noun pattern (e.g., get_collection, create_raindrop, delete_tags). The only minor deviation is plural vs. singular nouns (get_collection vs. get_collections), but this is a natural and predictable distinction for batch vs. single operations.
With 15 tools, the server is well-scoped for a bookmark manager: full CRUD for collections and raindrops, tag management, and user info. Each tool has a clear purpose, and the count is neither sparse nor overwhelming.
The tool surface covers the full lifecycle for collections, raindrops, and tags (create, read, update, delete, merge, rename). Search/filtering is integrated into get_raindrops, and user info is provided. There are no obvious missing operations for the domain.