Bookmarks Mcp

io.github.Fisher521Published by GitHub account Fisher521v0.1.0Updated Oct 25, 2026

Read-only MCP server for browser bookmarks: Chrome, Safari, Firefox, and read-later exports.

VerifiedSTDIODesktop onlyWeb Search & ScrapingFiles & Storage

Overview

AI-generated overview

A local, read-only MCP server that lets an assistant read browser bookmarks and read-later exports to search, summarize and triage them.

What you can do
List detected bookmark sources and browse bookmarks with folder filters and pagination, or search titles, URLs, folders and tags and pull recent saves and statistics such as counts, age and top domains. Parse export files from Pocket, Instapaper, Raindrop, browser HTML or URL lists. Export bookmarks as Markdown, CSV, JSON or importable browser HTML. Fetch a short preview of a bookmarked page (title, description, headings, excerpt) to judge whether it is worth reading.
When to use it
Useful when you want an assistant to make sense of a large or neglected bookmark collection: summarizing what you saved, finding old links, or turning the pile into a triage checklist of deep reads, tools to try and things to drop.
Requirements
Runs locally over stdio, typically via npx with no account, API key or configuration. Reads local browser profile files; on macOS, Safari bookmarks need Full Disk Access for the hosting app, and Firefox support needs Node 22.5 or newer. Network access only when a page preview is requested.
Before you install
Read-only toward browser files and has no delete tool, but export tools write files to disk. Page previews fetch the bookmarked site directly from your machine, so those URLs are disclosed to the sites involved; only public pages are supported. Bookmark data stays local otherwise.

Installation

In SourceWeft

  1. Open Bookmarks Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

bookmarks-mcp

Your bookmarks, wherever they live, readable by your AI.

Everyone saves. Browsers, read-later apps, that Pocket export from 2023 — capture is a solved problem. Processing is not: the average bookmark is saved once and never touched again. AI assistants are the first thing that can actually process a pile like that — summarize, triage, turn it into a to-do list — but they can't see it.

This is a local, read-only MCP server that fixes the "can't see it" part.

One command in your MCP client config. Zero accounts. Nothing is ever sent to us.

Sources

SourceHowNotes
Chrome, Edge, Brave, Arc, Vivaldi, Chromiumreads each profile's local Bookmarks fileevery profile auto-detected
Safari (macOS)reads ~/Library/Safari/Bookmarks.plistincludes your Reading List; no extension can do this — Safari's extension API has no bookmarks surface
Firefoxreads places.sqlite per profileneeds Node ≥ 22.5 (built-in sqlite); degrades gracefully below
Export filesPocket CSV, Instapaper CSV, Raindrop CSV, browser HTML, URL listsvia parse-bookmarks

Phone bookmarks: reachable once they sync to your desktop (iCloud → Safari on Mac, Chrome sync → desktop profile). There is no way for any third-party tool to read Safari bookmarks directly on iOS.

Install

No account, no API key, no configuration — the server works the moment it's installed.

Claude Code:

bash
claude mcp add -s user bookmarks -- npx -y bookmarks-mcp

Use -s user. The scope defaults to local, which only registers the server for the directory you ran the command in. Your bookmarks aren't tied to one project, so register it account-wide.

Claude Desktop / Cursor / any MCP client (mcpServers JSON):

json
{  "mcpServers": {    "bookmarks": {      "command": "npx",      "args": ["-y", "bookmarks-mcp"]    }  }}

To run from source instead (for development), clone this repo next to its dependency parse-bookmarks (the two directories must be siblings), run npm install in bookmarks-mcp, and point your client at node /absolute/path/to/bookmarks-mcp/src/index.js.

macOS + Safari: the app hosting the server (Claude Desktop, your terminal) needs Full Disk Access (System Settings → Privacy & Security), because ~/Library/Safari is protected. Chromium browsers and Firefox need nothing.

Tools

ToolWhat it does
list_sourcesevery bookmark source found on this machine
list_bookmarkslist, with folder filter + pagination
search_bookmarkssearch titles / URLs / folders / tags
recent_bookmarks"what did I save this week?"
bookmark_statsthe state of the pile: counts, age distribution, top domains
parse_export_fileparse a Pocket/Instapaper/Raindrop/HTML export from disk
export_bookmarkseverything out as Markdown, CSV, JSON, or importable browser HTML
fetch_page_previewa few-hundred-token preview of a page (title, description, headings, excerpt) instead of the raw HTML — for when title/URL alone can't be triaged

Turn the pile into a to-do list

The reason this exists. Ask your assistant:

Look at my bookmark stats, then help me triage: which of these become deep reads, which are tools to try, which feed a project I'm working on, and which should I finally let go? Give me a checklist for this week.

Or use the built-in triage_bookmarks prompt, which walks through exactly that — including asking you to define what your saves usually become, so the lanes are yours, not ours.

Guarantees

  • Read-only. This server never writes to a browser file. There is no delete tool. Your bookmarks cannot be harmed.
  • Zero phone-home. No telemetry, no accounts, and not a single byte sent to us. The server talks to exactly two places: your local bookmark files, and — only when you ask it to preview a page — the bookmarked site itself, directly from your machine.
  • Clean output. Tool results are data. No ads, no upsells, ever.

Design boundaries

These are deliberate, not gaps waiting to be filled. PRs that cross them will be declined:

  • Preview-level extraction only. fetch_page_preview answers "is this worth my time" — it is not a reader mode and never will be a full-fidelity content extractor.
  • Public web pages only. No proxies, no login walls, no special-casing for X/YouTube/WeChat/etc. If a page needs auth to read, this tool isn't the way in.
  • On-demand only. Nothing fetches in the background, ever. Every network call is a direct response to a tool call you made.

Roadmap

  • Cloud sources behind user-supplied tokens (Raindrop, Readwise, …) — one adapter per service. PRs welcome; an adapter is a single well-defined file.
  • Services that already ship their own MCP server don't need us — run both servers and your assistant sees everything. We only cover the places that have no other bridge.

Who makes this

Built by the team behind Burn 451, a read-later app. This server is deliberately neutral: it reads your bookmarks for whatever assistant and whatever workflow you choose, and it never writes to them.

License

MIT

Source: README.md at commit 8811dd0

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts