All servers · Tasks & projects
BriefMe
us.briefme/agenda-timer · v1.1.0
Has write/delete tools
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | extensions, prompts, resources, tools |
| Tool definitions | 12 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Connect
streamable-http · https://briefme.us/mcp
claude mcp add --transport http agenda-timer https://briefme.us/mcp{
"mcpServers": {
"agenda-timer": {
"url": "https://briefme.us/mcp"
}
}
}Tools as reported by the server
create_agendaCreates 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-ilist_agendasLists 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. Rget_agendaReads 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 BriefMget_shared_agendaReads the public agenda behind a BriefMe share link — the same blocks, timings and timer status the link's own page shows. Use when someone has a BriefMe share link and wants to know what is on the agenda, or how far along the meeting already is. Takes the share link, or just the token in it. It opeupdate_agendawrite/deleteRenames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda.add_blockAdds 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.update_blockwrite/deleteChanges 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 curremove_blockwrite/deleteRemoves 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.reorder_blocksPuts 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.rotate_edit_tokenwrite/deleteReplaces 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, unrelease_agendawrite/deleteTakes 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 idelete_agendawrite/deleteDeletes 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 acc
Website · JSON · Text for agents · Registry updated 2026-10-01