Karakeep MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KARAKEEP_API_KEY | Yes | Your Karakeep API token | |
| KARAKEEP_API_ADDR | Yes | The address of your Karakeep server |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-assetA | Get a temporary signed URL for downloading an asset by its asset ID. |
| search-bookmarksC | Search for bookmarks matching a specific query using full-text, semantic, or hybrid search. |
| get-bookmarkC | Get a bookmark by id. |
| get-bookmark-listsB | List every list that contains a bookmark. |
| create-bookmarkC | Create a link bookmark or a text bookmark |
| update-bookmarkA | Update fields on an existing bookmark. Only the fields you pass are modified; omitted fields stay unchanged. Returns the updated bookmark. |
| get-bookmark-contentB | Get the content of the bookmark in markdown |
| delete-bookmarkA | Delete a bookmark by id. This is destructive — the bookmark, its highlights, and its assets are removed. |
| list-highlightsA | List highlights across all bookmarks, newest first. |
| get-bookmark-highlightsC | List every highlight on a bookmark. |
| get-highlightB | Retrieve a single highlight by id. |
| create-highlightA | Create a text highlight on a bookmark using character offsets from the bookmark's readable content. |
| update-highlightB | Update a highlight's color or note. |
| delete-highlightC | Delete a highlight by id. |
| get-listsB | Retrieves a list of lists. |
| get-listB | Retrieve a single list by its id. |
| update-listA | Update a list. Only the fields you pass are changed. Length caps and smart-list query rules come from the shared list schema. |
| delete-listA | Delete a list by id. Bookmarks inside the list are not deleted. Child lists are also not deleted. Any child lists become root-level lists (their parentId is set to null). If that isn't the tree change you want, move or re-parent the children before calling this. |
| add-bookmark-to-listC | Add a bookmark to a list. |
| remove-bookmark-from-listC | Remove a bookmark from a list. |
| get-list-bookmarksA | List bookmarks in a list by its stable id. Smart lists are evaluated using their saved query. |
| create-listC | Create a list. |
| attach-tag-to-bookmarkC | Attach a tag to a bookmark. |
| detach-tag-from-bookmarkC | Detach a tag from a bookmark. |
| get-tagsB | List tags with their bookmark counts. Supports filtering and pagination. |
| get-tagA | Retrieve a single tag by id, including its bookmark counts. |
| update-tagB | Rename a tag. The new name is normalized by the server. |
| delete-tagB | Delete a tag by id. Bookmarks that had this tag are not deleted; the tag is just removed from them. |
| get-tag-bookmarksB | List bookmarks that have a given tag, with pagination. |
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 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.