Back to Home

MCP Server

26 tools for AI agents to search and reason over your reading history.

$ npx burn-mcp-server

Semantic search across bookmarks

Works with Claude, Cursor, Windsurf

Access Vault as structured data

Free tier included, no API key needed

View on npm →

Setup

You need a free Burn account (5 saves/day; Pro is $4.99/month for unlimited). Get your token in the app: Settings → MCP Server → Generate token → Copy.

Claude Desktop

{
  "mcpServers": {
    "burn": {
      "command": "npx",
      "args": ["burn-mcp-server"],
      "env": { "BURN_MCP_TOKEN": "<your-token>" }
    }
  }
}

Claude Code (CLI)

claude mcp add burn -e BURN_MCP_TOKEN=<your-token> -- npx burn-mcp-server

Cursor

Add the same JSON block to .cursor/mcp.json. Windsurf and any MCP-compatible client work identically.

What the 26 tools cover

Search & read (12) — query your Vault, Sparks, and Flame inbox; pull full article content.

Triage (5) — the agent reads your inbox and decides what to keep, up to 20 links at a time.

Collections (4) — create topic bundles and let the agent write synthesis overviews.

Auto-feed (4) + analysis (1) — watch X users, RSS feeds, or YouTube channels; new posts flow into your inbox.

Full tool reference lives in the GitHub README.

Example prompts

  • “Go through my Flame inbox, read each article, keep anything about AI agents and burn the rest.”
  • “Search my Vault for everything on context engineering and summarize the main schools of thought.”
  • “Create a collection called ‘MCP in production’ from my saves, then write an overview of what my sources agree and disagree on.”
  • “Add a watched source for Simon Willison’s blog so new posts land in my Flame.”
  • “I’m writing about read-later apps. Pull every relevant bookmark I have and list the claims I can support with a source.”

Burn MCP vs Raindrop MCP vs Readwise MCP

Three ways to give an AI agent access to your saved reading, honestly compared (verified July 2026):

ServerMaintained byWhat the agent getsWrite actionsCost to use
Burn MCPOfficial (open source, MIT)26 tools: reading queue, vault, full article content, collectionsEnforced triage flow, collections with AI overviews, watched sources (X/RSS/YouTube)All 26 tools on the free tier
Readwise MCPOfficial (hosted)Your Readwise highlights + Reader documentsHighlight/document-centric; no deadline queue to triageRequires a Readwise subscription (no permanent free tier)
Raindrop MCPCommunity (no official server)Bookmark library: collections, tags, highlights, searchBookmark/collection CRUD, tag management, duplicate cleanupFree with your Raindrop API token

The honest split: Readwise MCP is the pick if your value lives in years of highlights — it’s hosted, official, and highlight-native. The community Raindrop MCP servers make the agent a librarian for a large bookmark archive. Burn MCP is the only one built around a triage loop: the agent doesn’t just search your pile, it works the 24-hour queue with you — reading, keeping, and burning — and can auto-feed that queue from watched sources. If the pile is the problem, comparison over; if the pile is the point, pick by where your data already lives. Deeper dives: Burn vs Readwise · Burn vs Raindrop.

FAQ

Is the MCP server free?

Yes — all 26 tools are included in Burn’s free tier. The free tier is limited to 5 saves per day; Pro ($4.99/month) removes the limit.

Is my data safe?

Tokens are scoped to your own data via row-level security, rate-limited to 30 calls/min, and expire after 30 days. The server is open source (MIT).

How is this different from a bookmarking API?

MCP gives the agent structured tools, not raw endpoints — Claude can triage your inbox, curate collections, and cite your own saved sources without custom glue code. See the architecture write-up or how it fits a modern read-later stack.

Two other MCP servers, for bookmarks you never put in Burn

The server above reads your Burn library, so it needs an account and a token. If what you actually want is to point an AI assistant at the bookmarks already sitting in your browser, these two are separate open-source projects — no account, no token, and no network calls at all.

Bookmarks MCP

Read-only access to bookmarks in Chrome, Edge, Brave, Arc, Vivaldi, Firefox and Safari (including the Reading List), plus Pocket, Instapaper and Raindrop exports. Search and triage them from Claude, Cursor or Windsurf.

Bookmarks Lifecycle

Puts the same bookmarks on a decision clock — 24 hours to decide, 30 days to watch, or keep. It drips old bookmarks into a daily queue instead of dumping thousands on you, and it never deletes anything from your browser.