Karakeep MCP server
Related Servers
Alternatives to Karakeep MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to save and search bookmarks using OpenAI's RAG capabilities for intelligent bookmark management and retrieval.MIT
- AlicenseBqualityCmaintenanceEnables AI agents to manage bookmarks (webpages, articles, videos) on behalf of users, including registration, categorization, tagging, and sharing.2031 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables semantic search across browser bookmarks from Chrome, Firefox, Edge, Opera, and other browsers using natural language queries. Extracts and indexes bookmark content and metadata into a vector database for intelligent retrieval.1Apache 2.0
- AlicenseBqualityDmaintenanceEnables AI assistants to save and search bookmarks with semantic search using OpenAI, allowing storage of URLs with metadata and intelligent retrieval across collections.235 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceProvides authenticated bookmark management tools via MCP, including adding, deleting, listing, and searching bookmarks.2,274 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Anybox bookmark manager on macOS, allowing users to search, save, and organize bookmarks with tags and folders through natural language.16-
TDQS
Scored across 29 tools
Most tools map cleanly to a distinct resource+action (bookmark, list, tag, highlight, asset), and descriptions disambiguate the tricky pairs. However, the inverse-named pair get-bookmark-lists (lists containing a bookmark) vs get-list-bookmarks (bookmarks in a list) is easy to swap, and get-tags/get-tag plus list-highlights/get-bookmark-highlights sit close together.
Kebab-case verb_noun is used throughout, which is good, but the verb for collection retrieval is inconsistent: get-tags, get-lists, get-bookmark-lists use 'get' while list-highlights and get-list-bookmarks use 'list'/'get' in different orders. Noun ordering also flips between get-bookmark-lists and get-list-bookmarks, which undermines predictability in an otherwise uniform scheme.
At 29 tools the surface is on the heavy side, but the domain genuinely spans five resources (bookmarks, lists, tags, highlights, assets) with real CRUD, so most tools earn their place. A few could be collapsed (e.g. the collection-level getters) to trim the count.
Bookmarks, lists, tags, and highlights all have near-complete lifecycle coverage, including membership add/remove and search. The gaps are around assets: get-asset exists but nothing lists a bookmark's asset IDs or uploads assets, and there is no create-tag (tags only appear via attach), leaving minor dead ends agents must work around.