bookmarks-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sourcesA | Detect every bookmark source on this machine: Chromium-family profiles (Chrome, Edge, Brave, Arc, Vivaldi), Firefox profiles, and Safari (incl. Reading List). Returns ids usable as the |
| list_bookmarksB | List bookmarks from detected browsers. Supports folder filter and pagination. |
| search_bookmarksA | Case-insensitive search across bookmark titles, URLs, folders, and tags in every detected browser. |
| recent_bookmarksA | Bookmarks added in the last N days, newest first. Useful for |
| bookmark_statsA | The state of the pile: total count, per-source counts, age distribution (how much has sat untouched for years), and top domains. A good first call before triaging. |
| parse_export_fileA | Parse a bookmark export file from disk into clean JSON. Auto-detects: browser bookmark HTML (Netscape), Pocket CSV, Instapaper CSV, Raindrop CSV, or a plain URL list. |
| export_bookmarksA | Export bookmarks from detected browsers as markdown, csv, json, or importable browser HTML (Netscape format). Returns the file content; save it wherever you like. |
| fetch_page_previewA | Fetch a bookmarked URL and return a short, structured preview (title, description, headings, an opening excerpt, word count) instead of the raw page — a few hundred tokens instead of tens of thousands. Use this only when a title/URL alone isn't enough to triage a bookmark: dead links come back as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| triage_bookmarks | Turn the bookmark pile into decisions: ask the user what their saved things can become, classify every bookmark into those lanes, and produce actionable output per lane. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: listing, searching, recent, stats, parsing, exporting, previewing, and source detection. No two tools overlap in functionality, and the descriptions reinforce their unique roles.
Most tools follow a consistent verb_noun snake_case pattern (list_bookmarks, search_bookmarks, export_bookmarks). Two tools deviate slightly (recent_bookmarks, bookmark_stats) but remain readable and stylistically consistent.
Eight tools is a well-scoped count for a bookmark management server. Each tool addresses a distinct aspect of bookmark interaction without redundancy or bloat.
The tool set is heavily read-oriented with export and parsing utilities, but lacks write operations such as add, update, or delete bookmarks. Agents can identify dead links via fetch_page_preview but have no way to retire them, representing a significant functional gap.