BriefMe
by briefme.us · remote · no sign-in to list tools · v1.1.0 · published by us.briefme
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
12 tools: 6 can delete or cancel things, 1 do something that can't be undone, 2 change things and 3 only read.
Scanned Oct 21, 2026
- Deletes or cancels6Claude Code: deny: see these tools
- Can't be undone1Claude Code: ask: see these tools
- Changes things2Claude Code: ask: see these tools
- Only reads3Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http agenda-timer https://briefme.us/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnlist_agendas
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...unt, newest first, with the share_token every other tool takes. Useful at the start of a conver..."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
12 tools
Deletes or cancels 6Claude Code: deny
delete_agendaDeletes an agenda and its timer history permanently.No findings
Why it is in this group
- The name "delete_agenda" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Deletes an agenda and its timer history permanently. Its share and edit links stop working the moment this returns, and nothing can be recovered. Meant for an agenda the user has explicitly confirmed; the delete-agenda skill asks first. release_agenda instead takes a saved agenda out of a linked account and keeps its share link alive for a while. Returns {deleted: true, share_token}.
Annotations the server declares
- title: Delete an agenda
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
release_agendaTakes one agenda out of the BriefMe account to free a slot.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Takes one agenda out of the BriefMe account to free a slot. The agenda is not deleted now: its share link keeps working for 7 more days and then it expires like any anonymous agenda. The release is final — a released agenda cannot be returned to the account and list_agendas no longer shows it — so it fits an agenda the user has explicitly chosen to drop.
Annotations the server declares
- title: Remove an agenda from the account
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
remove_blockRemoves one block from an agenda.No findings
Why it is in this group
- The name "remove_block" says "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Removes one block from an agenda. The remaining blocks keep their ids and their order. An agenda must keep at least one block, so this fails on the last one. Removing a block shortens the meeting — it does not redistribute that time to the other blocks. Returns the full updated agenda.
Annotations the server declares
- title: Remove a block
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
rotate_edit_tokenReplaces an agenda's edit token and edit link with new ones.No findings
Why it is in this group
- The name "rotate_edit_token" says "edit": a word for a change.
- The description says "cannot be restored".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Replaces an agenda's edit token and edit link with new ones. The previous edit_token and edit_url stop working the moment this returns, for every assistant, browser and bookmark that held them — the remedy when an edit link was shared by mistake. Returns the full agenda with the new edit_url and, unless the agenda is saved to a linked BriefMe account, the new edit_token. The previous ones cannot be restored. Agendas expire after 7 days and cannot be recovered afterwards.
Annotations the server declares
- title: Regenerate the edit link
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
update_agendaRenames the agenda.No findings
Why it is in this group
- The name "update_agenda" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Renames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda.
Annotations the server declares
- title: Rename a meeting agenda
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_blockChanges one block, identified by block_id.No findings
Why it is in this group
- The name "update_block" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Changes one block, identified by block_id. Only the supplied fields change; anything omitted keeps its current value exactly, so a one-field edit is a one-field call. Changes one block only: it does not reorder, add or remove anything, and there is no whole-agenda replace. get_agenda returns the current block ids. Returns the full updated agenda.
Annotations the server declares
- title: Change one block
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
create_agendaCreates a timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync.No findings
Why it is in this group
- The name "create_agenda" says "create": a word for a change.
- The description says "cannot be recovered".
Description, as the server wrote it Creates a timed meeting agenda — a shareable countdown timer that walks attendees through timeboxed topics in sync. Use when the user wants a meeting timer, timeboxes, a run of show, a workshop or standup schedule, or to keep a meeting on time. Not for calendar scheduling or note-taking, and a two-item chat needs no timer. Returns share_token (what later calls take), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand). Without a linked BriefMe account it also returns edit_token, which later calls take instead of an account. The user needs both links. When the blocks depart from BriefMe's standard shape — an opening, a wrap-up, planned breaks — the result also carries structure_suggestions, each naming the block to add and its length; add_block and reorder_blocks apply them. Block durations add up to the meeting length; when none is given, a standup is about 15 minutes, a 1:1 about 30, sprint planning 60 to 90. Most agendas are three to eight blocks. Titles are read off a wall-sized countdown, so six words or fewer read best; a description is useful only when the title alone is ambiguous. Include the opening, the wrap-up and any planned break in this first call: every change afterwards is a separate confirmation for the user. Agendas expire after 7 days and cannot be recovered afterwards.
Annotations the server declares
- title: Create a meeting agenda
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
add_blockAdds one block to an existing agenda: at the end, above a final wrap-up, or directly after after_block_id.No findings
Why it is in this group
- The name "add_block" says "add": a word for a change.
Description, as the server wrote it Adds one block to an existing agenda: at the end, above a final wrap-up, or directly after after_block_id. Adds only — it does not reorder or change any existing block. Returns the full updated agenda, so no get_agenda call is needed afterwards.
Annotations the server declares
- title: Add a block to an agenda
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
reorder_blocksPuts the agenda's blocks into the order given.No findings
Why it is in this group
- The description's first verb is "put": a word for a change.
Description, as the server wrote it Puts the agenda's blocks into the order given. block_ids must contain every current block id exactly once — none missing, none extra, none repeated. This only reorders: it cannot add, remove or edit a block. get_agenda returns the current ids. Returns the full updated agenda.
Annotations the server declares
- title: Reorder the blocks of an agenda
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Claude Code: allow
get_agendaReads back the current state of an agenda, including the id of every block.No findings
Why it is in this group
- The name "get_agenda" says "get": a word for reading.
Description, as the server wrote it Reads back the current state of an agenda, including the id of every block. Needed when block ids are unknown — for example at the start of a new conversation; after any BriefMe mutation the current state is already in hand. Identifies the agenda by share_token for an agenda saved to a linked BriefMe account, or by the edit_token create_agenda returned, which authorizes on its own. A share link alone does not open an agenda for editing: get_shared_agenda reads the public agenda behind one, without edit access.
Annotations the server declares
- title: Read a meeting agenda
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_agendasLists every agenda saved in the signed-in BriefMe account, newest first, with the share_token every other tool takes.1 finding
Why it is in this group
- The name "list_agendas" says "list": a word for reading.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...unt, newest first, with the share_token every other tool takes. Useful at the start of a conver..."
Description, as the server wrote it Lists every agenda saved in the signed-in BriefMe account, newest first, with the share_token every other tool takes. Useful at the start of a conversation when the user refers to an agenda made earlier ("run last week's sprint planning again"), and after create_agenda reports the account is full. Returns limit, retained and slots_left alongside the agendas. It returns share links only — the private control link comes from create_agenda.
Annotations the server declares
- title: List the account's agendas
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agenda-timer https://briefme.us/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__agenda-timer__list_agendas",
"mcp__agenda-timer__get_agenda",
"mcp__agenda-timer__get_shared_agenda"
],
"ask": [
"mcp__agenda-timer__create_agenda",
"mcp__agenda-timer__add_block",
"mcp__agenda-timer__reorder_blocks"
],
"deny": [
"mcp__agenda-timer__update_agenda",
"mcp__agenda-timer__update_block",
"mcp__agenda-timer__remove_block",
"mcp__agenda-timer__rotate_edit_token",
"mcp__agenda-timer__release_agenda",
"mcp__agenda-timer__delete_agenda"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agenda-timer. Review it before you use it.