Raindrop.io MCP Server
Related Servers
Alternatives to Raindrop.io MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables language models to access and manage Raindrop.io bookmarks, collections, tags, and highlights through the Model Context Protocol.34 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access and manage Raindrop.io bookmarks, collections, tags, and highlights through the Model Context Protocol. Supports CRUD operations, advanced search, file uploads, and bulk editing of bookmarks.44 npmMIT
- FlicenseAqualityDmaintenanceEnables to manage Raindrop.io bookmarks programmatically—add, search, and organize bookmarks from LLM apps.413-
- AlicenseAqualityBmaintenanceEnables searching and managing Raindrop.io bookmarks via the official REST API, including listing collections, retrieving bookmarks, and creating or updating bookmarks.5MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server implementation that provides seamless integration between Chrome bookmarks and AI assistants. This server enables AI models to access, search, analyze, and manage Chrome bookmarks through a standardized protocol.2MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides persistent storage, categorization, and retrieval of bookmarks through AI clients like Claude. It allows users to manage web links using custom categories and includes options for local JSON storage or AWS S3 synchronization.217Apache 2.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create-bookmark for adding new bookmarks, list-collections for viewing collections, and search-bookmarks for finding existing bookmarks. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (create-bookmark, list-collections, search-bookmarks) with hyphens used uniformly. This predictable naming scheme enhances readability and usability for agents.
With only 3 tools, the server feels thin for a bookmark management domain, lacking essential operations like update, delete, or get specific bookmarks/collections. While the tools cover basic actions, the count is borderline low for comprehensive functionality.
The tool surface has significant gaps for a bookmark manager: no update-bookmark, delete-bookmark, get-bookmark, or get-collection tools, and no lifecycle management for collections. This incomplete coverage will likely cause agent failures in common workflows like editing or removing bookmarks.