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 obtained from the Raindrop.io Developer Portal |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_root_collectionsB | Get all root collections from Raindrop.io |
| get_child_collectionsB | Get all child collections from Raindrop.io |
| get_collection_by_idC | |
| create_collectionA | |
| update_collectionB | |
| delete_collectionB | |
| empty_trashB | Empty the trash in Raindrop.io, permanently deleting all raindrops in it. |
| get_raindropA | |
| get_raindropsA | |
| get_tagsB | |
| update_raindropB | |
| update_many_raindropsB | |
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 12 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in the Raindrop.io domain. For example, get_raindrop retrieves a single item while get_raindrops fetches multiple with filtering, and update_raindrop modifies one while update_many_raindrops handles batch operations. There is no functional overlap that would cause confusion.
All tools follow a consistent verb_noun naming pattern with snake_case throughout (e.g., create_collection, get_raindrops, update_many_raindrops). The verbs (create, delete, get, update, empty) are appropriately chosen for their actions, and nouns (collection, raindrop, tags, trash) clearly identify the resources being manipulated.
With 12 tools, this server is well-scoped for managing Raindrop.io collections and raindrops. It covers core operations like CRUD for collections and raindrops, plus utilities like trash management and tag retrieval. Each tool serves a distinct purpose without being excessive or insufficient for the domain.
The tool set provides comprehensive coverage for the Raindrop.io domain, including full CRUD for collections and raindrops, batch operations, trash management, and tag retrieval. A minor gap is the lack of a tool to create new raindrops, which might require agents to work around by using update operations or external methods, but core workflows are well-supported.