
Burn Mcp Server
- 1 repo stars
- Updated July 23, 2026
- Fisher521/burn-mcp-server
Burn MCP server is an MCP integration that provides 26 AI-powered reading-triage tools with a 24-hour burn timer so agents help you read less and retain more.
About
Burn MCP server connects coding agents to the Burn reading-triage product: 26 tools backed by a 24-hour burn timer so saved links do not rot in an infinite backlog. developers researching markets, stacks, or competitors install it when IDE chat should pull from a disciplined reading queue instead of ad-hoc paste dumps. You can run burn-mcp-server locally via npm stdio or use the hosted streamable-http remote at burn-mcp-server.vercel.app with Authorization Bearer and a long-lived BURN_MCP_TOKEN from burn451.cloud Settings. The workflow suits research and ongoing learning, not production monitoring. It complements bookmarks and RSS by adding agent-addressable triage, summarization, and expiry semantics your client can orchestrate. It does not replace a full knowledge base or team wiki. Choose stdio for offline-first dev machines or HTTP when you prefer hosted transport; keep tokens secret like any production API key.
- 26 MCP tools for reading triage and queue management
- 24-hour burn timer to force read-or-drop decisions
- stdio npm package and remote streamable-http endpoint
- Bearer BURN_MCP_TOKEN from burn451.cloud Settings
- Positioned as read less, absorb more for busy builders
Burn Mcp Server by the numbers
- Data as of Jul 23, 2026 (Skillselion catalog sync)
claude mcp add --env BURN_MCP_TOKEN=YOUR_BURN_MCP_TOKEN burn-mcp-server -- npx -y burn-mcp-serverAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | burn-mcp-server |
| Transport | STDIO, HTTP |
| Auth | Required |
| Last updated | July 23, 2026 |
| Repository | Fisher521/burn-mcp-server ↗ |
What it does
Triage articles and long reads through Burn’s AI reading queue so your agent summarizes, prioritizes, and expires low-value items on a 24-hour burn timer.
Who is it for?
Best when you're drowning in research links and want Claude Code or Cursor to operate a timed reading inbox.
Skip if: Skip if you need enterprise document management, compliance archiving, or non-Burn reading workflows.
What you get
After registration, your agent can manage Burn’s triage queue, act on items before they expire, and return denser summaries for decision-making.
- Agent-managed Burn reading queue with expiry discipline
- Summaries and triage actions across 26 documented tools
- Less tab sprawl during market and tech research
By the numbers
- 26 MCP tools described in server metadata
- 24-hour burn timer is a core product behavior
- Server version 2.1.0 with stdio npm and optional HTTP remote
README.md
Burn — Personal Knowledge Base MCP Server
Your reading data as an AI-accessible knowledge base. 26 tools for Claude, Cursor, Windsurf, and any MCP-compatible agent.
How it works
Burn triages your reading with a 24h timer:
- Flame → New links. 24h to read or they burn.
- Spark → You read it. Stays 30 days.
- Vault → Permanent. Your curated knowledge.
- Ash → Expired. They had their chance.
The MCP server lets your AI agent search, triage, organize, and analyze everything you've saved.
Quick Start
1. Get your token
Download Burn on iOS or use Burn on the web → Settings → MCP Server → Copy Access Token
2. Pick a connection mode
2a. Local — stdio (Claude Desktop / Claude Code CLI / Cursor / Windsurf)
{
"mcpServers": {
"burn": {
"command": "npx",
"args": ["burn-mcp-server"],
"env": {
"BURN_MCP_TOKEN": "<your-token>"
}
}
}
}
2b. Remote — HTTPS (claude.ai Connectors / Claude Code Routines / any cloud MCP client)
Endpoint:
https://burn-mcp-server.vercel.app/api/mcp
Auth: Authorization: Bearer <BURN_MCP_TOKEN> header.
For claude.ai Connectors (Settings → Connectors → Add custom MCP):
- URL:
https://burn-mcp-server.vercel.app/api/mcp - Header:
Authorization: Bearer <your BURN_MCP_TOKEN>
For Claude Code Routines: link globally in Settings → Connectors; Routines will auto-include it.
Direct curl test:
curl -X POST https://burn-mcp-server.vercel.app/api/mcp \
-H "Authorization: Bearer $BURN_MCP_TOKEN" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'
Transport: stateless StreamableHTTP, JSON-response mode. Same 26 tools, same token, no install.
3. Start asking
- "What did I save about system design?"
- "Triage my Flame — what should I keep?"
- "Create a collection from my AI bookmarks"
Tools (26)
Search & Read
| Tool | What it does |
|---|---|
search_vault |
Search permanent bookmarks by keyword |
list_vault |
List Vault bookmarks by category |
list_sparks |
List recently read bookmarks (30-day window) |
search_sparks |
Search Sparks by keyword |
list_flame |
List inbox — what's about to burn |
get_flame_detail |
Full detail on a Flame bookmark |
get_bookmark |
Get any bookmark by ID |
get_article_content |
Get full article content + analysis |
fetch_content |
Fetch content from a URL (X, Reddit, YouTube, WeChat) |
list_categories |
All Vault categories with counts |
get_collections |
List all Collections |
get_collection_overview |
Collection detail with AI overview |
Triage (Agent as your filter)
| Tool | What it does |
|---|---|
move_flame_to_spark |
Keep it — worth reading. Optional insight. |
move_flame_to_ash |
Burn it. Optional reason. |
move_spark_to_vault |
Promote to permanent. Optional category. |
move_spark_to_ash |
Not valuable enough to keep. |
batch_triage_flame |
Triage up to 20 at once. |
Collections (Agent as your curator)
| Tool | What it does |
|---|---|
create_collection |
Create a topic bundle with initial bookmarks |
add_to_collection |
Add bookmarks (deduplicates) |
remove_from_collection |
Remove bookmarks |
update_collection_overview |
Write AI overview (theme, synthesis, gaps) |
Analysis (Agent as your analyst)
| Tool | What it does |
|---|---|
write_bookmark_analysis |
Write structured analysis back to a bookmark |
Auto-Feed (Agent as your scout)
| Tool | What it does |
|---|---|
add_watched_source |
Watch an X user, RSS feed, or YouTube channel. New posts flow into Flame automatically. |
list_watched_sources |
List all active watched sources |
remove_watched_source |
Stop watching a source |
scrape_watched_sources |
Fetch new content from watched sources on demand |
Resources
| URI | Content |
|---|---|
burn://vault/bookmarks |
All Vault bookmarks (JSON) |
burn://vault/categories |
Category list (JSON) |
Use Cases
Personal knowledge management — Your agent searches your reading history to answer questions, find patterns, and surface forgotten gems.
Research workflows — Create collections on topics you're exploring. Agent writes overviews synthesizing your sources.
Reading triage — Agent reviews your Flame inbox, reads the content, decides what's worth keeping based on your interests.
Cross-tool intelligence — Use with Claude Code, Cursor, or Windsurf. Your bookmarks become context for coding, writing, and thinking.
Environment Variables
| Variable | Required | Description |
|---|---|---|
BURN_MCP_TOKEN |
Yes* | Long-lived MCP token (recommended) |
BURN_SUPABASE_TOKEN |
Yes* | Legacy JWT token (still supported) |
BURN_API_URL |
No | Custom API URL (default: production) |
*One of BURN_MCP_TOKEN or BURN_SUPABASE_TOKEN required.
Security
- Token scoped to your data only (Row Level Security)
- Status flow enforced: Flame → Spark → Vault, or → Ash
- Rate limit: 30 calls/min per session
- Tokens expire after 30 days
Links
- App: burn451.cloud
- iOS App: App Store
- npm: burn-mcp-server
- Chrome Extension: Search "Bookmark Autopsy" on Chrome Web Store
License
MIT
Recommended MCP Servers
How it compares
Reading-triage MCP product bridge, not a codebase search or documentation generator skill.
FAQ
Who is Burn MCP server for?
Developers and researchers who use Burn451 and want agent-driven triage of articles and long reads with a 24-hour burn window.
When should I use Burn MCP server?
Use it during Idea research—or anytime you ingest heavy reading—when you want the agent to prioritize, summarize, and clear queue items before they burn.
How do I add Burn MCP server to my agent?
Generate BURN_MCP_TOKEN at burn451.cloud → Settings → MCP Server, then either install burn-mcp-server npm with stdio or configure the remote URL with Authorization Bearer header per your MCP client.