bookmark-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host for HTTP server (HTTP only). | 127.0.0.1 |
| PORT | No | Port for HTTP server (HTTP only). | 3000 |
| LOG_LEVEL | No | Log level: debug, info, warn, error. | info |
| BOOKMARKS_FILE | No | Path to the bookmarks JSON file. | ./data/bookmarks.json |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_bookmarkA | Save a URL to the user's reading list. Rejects duplicate URLs. Returns the created bookmark including its generated id. |
| search_bookmarksA | Search the reading list by free text, tag, and/or read status. Call without arguments to list the most recent bookmarks. |
| mark_readA | Mark a bookmark as read. Safe to call repeatedly. |
| delete_bookmarkA | Permanently delete a bookmark from the reading list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| reading_digest | Build a prioritized digest of unread bookmarks, optionally scoped to one tag. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-bookmarks | The complete reading list as JSON, newest first. |
| bookmark-stats | Totals and per-tag counts for the reading list. |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: add, delete, mark as read, and search. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern: add_bookmark, delete_bookmark, mark_read, search_bookmarks. The pattern is uniform and intuitive.
Four tools is an appropriate scope for a bookmark manager, covering essential operations without unnecessary bloat.
The tool set covers the basic CRUD and search functionality. A minor gap is the lack of an update tool for bookmark metadata beyond read status, but the core is solid.