mcp-bookmark
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | Required for AI-powered categorization and search enhancement |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_bookmarkC | Save a bookmark to the vector store. |
| search_bookmarkC | Search for bookmark in the vector store. |
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 2 tools
Save and search are clearly distinct actions with no overlap. An agent can easily determine which tool to use based on whether it needs to add or find a bookmark.
Both tools follow a consistent verb_noun pattern (save_bookmark, search_bookmark), making the naming predictable and intuitive.
With only two tools, the server feels thin for a bookmarking domain. While save and search are core operations, a typical bookmark manager would likely require more tools, making the count borderline.
The tool surface is significantly incomplete. It offers only create (save) and search, but lacks essential operations like list, delete, and update, which would cause agent failures when those actions are needed.