briefing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRIEFING_KEY | No | Optional Reader key (sent as `Authorization: Bearer`). Set it to enable unlimited reads, Morning Paper delivery, and 10 custom renders/day. | |
| BRIEFING_BASE_URL | No | Override the API base URL. Default is the public Briefing Service. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_briefingsB | List the hourly briefings available (key and name), with prices. |
| get_briefingB | One briefing as structured JSON: lead story, ranked stories and research items with summaries, why-it-matters and key points, plus when it was ranked. |
| get_summaryB | Free, small: headlines and one-line summaries of a briefing (for widgets and quick reads). |
| get_candidatesB | Free provenance dump: every candidate the editor saw this hour with canonical_link, published time, feed weight, the other outlets that ran the story (also_in), a selected flag, and collapsed duplicates (duplicate_of, dup_rule, dup_score). |
| get_pageA | One rendered page of a briefing as a 480x800 1-bit PNG (page 0 is the front page; story pages follow). Made for e-ink and small displays. wide=true returns the 800x480 landscape front page. |
| render_briefingB | Rank and render a briefing from your own feeds and persona (one editor run; needs a Reader key with render credits, or use x402 on the remote endpoint). Returns JSON and page URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct facet: listing, full JSON, lightweight summary, provenance candidates, image pages, and rendering. The only mild overlap is get_summary vs get_briefing, but the descriptions make the size/format tradeoff clear enough to choose correctly.
All six tools follow a strict verb_noun snake_case pattern (list_briefings, get_briefing, get_summary, get_candidates, get_page, render_briefing). No style mixing or vague standalone verbs.
Six tools is well-scoped for a briefing service, with one clear tool per access mode (list, full read, quick summary, provenance, visual page, render). Nothing feels padded or missing from the count.
The surface covers discovery, full and lightweight retrieval, provenance, paginated rendering, and custom rendering. Minor gaps exist (no date-range search or explicit pagination for list_briefings, and only passive retrieval of pages), but core workflows are covered.