geekmonks-mcp-bookmarks
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_bookmarksA | List all saved bookmarks from the local JSON store. |
| add_bookmarkA | Add a bookmark with a title and URL to the local JSON store. |
| search_bookmarksA | Search bookmarks by substring match on title or URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-bookmarks | Ask the model to summarize saved bookmarks and suggest what to read next. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bookmarks-catalog | Full local bookmarks JSON catalog |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing, adding, and searching bookmarks. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_bookmarks, add_bookmark, search_bookmarks. The pattern is clear and predictable.
With only 3 tools, the server is minimal but covers the basic operations for a bookmark store. It feels slightly thin but is reasonable for a simple local JSON store.
The server provides list, add, and search, but lacks update and delete operations, which are common for bookmark management. This is a notable gap but agents can work around it by not needing those operations.