burn-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BURN_MCP_TOKEN | Yes | Dedicated Burn test-account MCP token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vaultA | Search your Burn Vault for bookmarks by keyword (searches title, tags, AI takeaway) |
| list_vaultB | List bookmarks in your Vault, optionally filtered by category |
| list_sparksA | List your Sparks (bookmarks you have read, with 30-day lifespan). Includes spark insight and expiry date. |
| search_sparksA | Search your Sparks by keyword (searches title, tags, AI takeaway, spark insight) |
| get_bookmarkA | Get full details of a single bookmark including AI analysis and extracted content |
| get_article_contentA | Get full article content and AI analysis for a bookmark by ID (same as get_bookmark) |
| fetch_contentA | Fetch article/tweet content from a URL. Works with X.com (bypasses GFW via proxy), Reddit, YouTube, Bilibili, WeChat, and any web page. First checks Supabase cache, then fetches live. |
| list_categoriesA | List all Vault categories with article counts |
| list_flameA | List bookmarks in your Flame inbox (24h countdown). Shows AI triage info (strategy, relevance, novelty, hook) and time remaining. Use this to see what needs attention before it burns to Ash. |
| get_flame_detailA | Get full details of a Flame bookmark including extracted article content, AI analysis, and reading guidance. Use this to deep-read a bookmark before deciding its fate. |
| get_collectionsA | List all your Collections with article counts and AI overview themes |
| get_collection_overviewA | Get a Collection by name with its AI overview and linked bookmarks metadata |
| move_flame_to_sparkA | Move a Flame bookmark to Spark (mark as worth reading). Sets 30-day Spark lifespan. |
| move_flame_to_ashB | Burn a Flame bookmark to Ash (not worth keeping). |
| move_spark_to_vaultB | Promote a Spark bookmark to permanent Vault storage. |
| move_spark_to_ashB | Burn a Spark bookmark to Ash (not valuable enough to vault). |
| batch_triage_flameA | Triage multiple Flame bookmarks at once. Each decision moves a bookmark to Spark or Ash. |
| write_bookmark_analysisA | Write AI analysis results into a bookmark. Agent analyzes content with its own LLM, then writes structured results back to Burn. Only provided fields are merged — existing data is preserved. |
| create_collectionA | Create a new Collection to group related bookmarks together. |
| add_to_collectionA | Add bookmarks to an existing Collection. Duplicates are silently ignored. |
| remove_from_collectionB | Remove bookmarks from a Collection. |
| update_collection_overviewA | Write an AI-generated overview for a Collection (theme, synthesis, patterns, gaps). |
| add_watched_sourceA | Watch an X user, RSS feed, or YouTube channel — new posts auto-appear in Burn Flame on each scrape. |
| list_watched_sourcesA | List all active watched sources (X users, RSS feeds, YouTube channels). |
| remove_watched_sourceA | Stop watching a source. Use list_watched_sources to find the source ID. |
| scrape_watched_sourcesA | Fetch new content from all watched sources (or one specific source) and add new items to Burn Flame. Call this on a schedule or on demand. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| vault-bookmarks | |
| vault-categories |
TDQS
Scored across 26 tools
Several tools have clear boundaries (e.g., move_flame_to_spark vs move_flame_to_ash), but get_bookmark and get_article_content are explicitly identical, and list_vault/search_vault plus list_sparks/search_sparks overlap heavily. The descriptions help, but the duplicate is a direct ambiguity.
Most tools follow a consistent verb_noun snake_case pattern (search_vault, list_sparks, create_collection). Minor deviations exist: 'get_collections' is actually a list operation, and 'fetch_content' uses a different verb than 'get_article_content', but these are small and do not undermine the overall consistency.
With 26 tools, the count exceeds the 25+ threshold for being too heavy. Many operations are repetitive (e.g., individual moves vs batch_triage) and could be consolidated, making the surface feel bloated for what is essentially a bookmark management domain.
The lifecycle (Flame to Spark to Vault to Ash) is well covered, but there is no explicit 'create bookmark' tool since fetch_content only fetches and doesn't necessarily save. Additionally, there are no update or delete operations for bookmarks, and no way to remove a bookmark from the Vault or delete collections, leaving significant gaps.