1BRI_API_KEY='bri_your-key-here' bri mcp
bri login. A typical client configuration has this shape:1234567891011{ "mcpServers": { "bri": { "command": "bri", "args": ["mcp"], "env": { "BRI_API_KEY": "bri_your-key-here" } } } }
https://bri.fyi/mcp. It accepts stateless JSON MCP requests over POST:12Authorization: Bearer bri_your-key-here Content-Type: application/json
GET /mcp returns discovery metadata. Bri does not expose an SSE session transport here; clients should use the JSON response mode.list_notes lists active or deleted notes; it needs read permission.read_note reads a note by username and slug; it needs read permission for protected content.publish_note publishes Markdown and creates external state; it needs write permission.list_note_versions lists version metadata; it needs read permission.read_note_version reads a complete snapshot; it needs read permission.restore_note_version changes the current note; it needs write permission.read_write key when an agent needs the complete tool set. A read-only key is safer for research or summarization agents; it cannot publish or restore.publish_note or restore_note_version, and keep keys scoped to the smallest set of tools the workflow needs.