Does Raindrop.io have an MCP server?

Yes. Raindrop.io ships an official MCP at https://api.raindrop.io/rest/v2/ai/mcp (Streamable HTTP, OAuth 2.1), documented tools cover bookmarks, collections, tags, highlights, and account data. See help.raindrop.io/integrations/mcp. Burn 451 also ships MCP (burn-mcp-server on npm), but the surface is different: Burn's MCP exposes the Flame/Spark/Vault decision loop and 24-hour triage state, not a bookmark archive. Both are MCP — pick on what you want the model to see.

What is the difference between Raindrop and Burn 451?

Raindrop.io is a bookmark archive/library — save, organize, and keep links forever with collections, tags, broken-link checks, and search across everything you've ever stored. Burn 451 is a read-later triage app with a 24-hour timer that forces a decision on every save: read it, vault it, or let it burn. Same input (a saved URL), opposite output workflow.

Can you use Burn 451 and Raindrop together?

Yes — and it's a sensible pair. Burn 451 as the triage inbox (everything runs the 24-hour timer first), Raindrop as the permanent archive/library you commit to. Each has its own MCP, so an AI client can see both surfaces if you want: Burn's decision loop and Raindrop's archive index.

Burn 451 vs Raindrop.io 2026: Archive Library vs 24-Hour Triage Queue

Both ship MCP — fork is workflow

Raindrop.io is a bookmark archive/library with collections, tags, and an official MCP over the bookmark index. Save things you want to keep forever.

Burn 451 is a read-later triage app with a 24-hour timer and an MCP over the Flame/Spark/Vault decision loop. Save things you want to make a decision about.

Same input (a URL). Opposite output (keep forever vs. decide in 24 hours).

Raindrop.io is a bookmark archive/library. Burn 451 is a read-later triage app. They overlap — both save URLs, both have browser extensions, both have iOS apps, and as of 2026 both expose an MCP server — but they solve different problems.

What Raindrop does well

Visual organization and durable archive. You get nested collections, color tags, cover images, full-text search across everything you've ever saved, and broken-link detection on Pro. Pricing on raindrop.io is free + Pro (verify current Pro price on the official Pro page). It's genuinely good for people who curate link libraries — design inspiration, research archives, company resource hubs.

What Burn 451 does differently

Every save gets a 24-hour timer. You have to decide — read it, vault it, or burn it. There's no infinite archive because the mechanics don't allow passive accumulation. Burn also generates an AI 3-bullet summary on save and has a free tier today (planned V3 Pro $4.99/mo or $48/yr, planned not live).

Does Raindrop have an MCP server?

Yes. Raindrop ships an official MCP at api.raindrop.io/rest/v2/ai/mcp over Streamable HTTP with OAuth 2.1. The documented tools cover bookmarks, collections, tags, highlights, and account data — i.e. the archive surface. Burn 451 also ships MCP (burn-mcp-server on npm), but the surface is the Flame/Spark/Vault decision loop: what's in active triage, what survived to Spark, what made it to Vault. Two MCPs, two different model views — pick on what you want Claude or Cursor to see.

The overlap question

Both tools can technically save articles. The difference is intent. Raindrop assumes you want to keep and organize. Burn assumes you want to read and decide. If your use case is "I need to find that article about [topic] from two years ago," Raindrop wins. If your use case is "I keep saving things I never read," Burn wins.

Where Burn falls short

Burn is not an archive — by design, you cannot accumulate a permanent searchable library of everything you ever saved. The 24h timer is opinionated and not for everyone. No nested collections, no color tags, no permanent organization UI. If your problem is "I have 5,000 useful links and I need them organized," Raindrop is the right answer and Burn will feel hostile.

Can you use both?

Yes — and it's a sensible pair. Burn 451 as the triage inbox (everything runs the 24h timer first), Raindrop as the permanent archive/library you commit to. With both MCPs configured, an AI client can see both surfaces: Burn's active decision loop and Raindrop's long-term index. See also: Best Chrome Bookmark Extension 2026 — save to either tool in one click. If you're specifically deciding Raindrop vs Pocket post-shutdown, see Raindrop vs Pocket 2026 for the head-to-head migration angle.