Burn Mcp Server

Created By
Fisher5212 months ago
Overview

Burn — Personal Knowledge Base MCP Server

npm version License: MIT

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

ToolWhat it does
search_vaultSearch permanent bookmarks by keyword
list_vaultList Vault bookmarks by category
list_sparksList recently read bookmarks (30-day window)
search_sparksSearch Sparks by keyword
list_flameList inbox — what's about to burn
get_flame_detailFull detail on a Flame bookmark
get_bookmarkGet any bookmark by ID
get_article_contentGet full article content + analysis
fetch_contentFetch content from a URL (X, Reddit, YouTube, WeChat)
list_categoriesAll Vault categories with counts
get_collectionsList all Collections
get_collection_overviewCollection detail with AI overview

Triage (Agent as your filter)

ToolWhat it does
move_flame_to_sparkKeep it — worth reading. Optional insight.
move_flame_to_ashBurn it. Optional reason.
move_spark_to_vaultPromote to permanent. Optional category.
move_spark_to_ashNot valuable enough to keep.
batch_triage_flameTriage up to 20 at once.

Collections (Agent as your curator)

ToolWhat it does
create_collectionCreate a topic bundle with initial bookmarks
add_to_collectionAdd bookmarks (deduplicates)
remove_from_collectionRemove bookmarks
update_collection_overviewWrite AI overview (theme, synthesis, gaps)

Analysis (Agent as your analyst)

ToolWhat it does
write_bookmark_analysisWrite structured analysis back to a bookmark

Auto-Feed (Agent as your scout)

ToolWhat it does
add_watched_sourceWatch an X user, RSS feed, or YouTube channel. New posts flow into Flame automatically.
list_watched_sourcesList all active watched sources
remove_watched_sourceStop watching a source
scrape_watched_sourcesFetch new content from watched sources on demand

Resources

URIContent
burn://vault/bookmarksAll Vault bookmarks (JSON)
burn://vault/categoriesCategory 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

VariableRequiredDescription
BURN_MCP_TOKENYes*Long-lived MCP token (recommended)
BURN_SUPABASE_TOKENYes*Legacy JWT token (still supported)
BURN_API_URLNoCustom 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

License

MIT

Project Info
Created At
2 months ago
Updated At
a month ago
Author Name
Fisher521
Star
-
Language
-
License
-
Category
Tags

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago