BriefMe
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Connect it
Settings → Connectors → Add custom connector
URL: https://briefme.us/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://briefme.us/mcp{
"mcpServers": {
"agenda-timer": {
"url": "https://briefme.us/mcp"
}
}
}claude mcp add --transport http agenda-timer https://briefme.us/mcp{
"servers": {
"agenda-timer": {
"type": "http",
"url": "https://briefme.us/mcp"
}
}
}12 tools, verified live
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-item chat needs no timer. Returns share_token (what later calls take), share_url (the read-only live
list_agendasread-onlyLists 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 pri
get_agendaread-onlyReads 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 a
get_shared_agendaread-onlyReads 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 opens nothing else: it grants no edit access, the agenda cannot be changed through it, and it returns
update_agendacan modifyRenames 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_blockcan modifyChanges 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.
remove_blockcan modifyRemoves 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_tokencan modifyReplaces 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
release_agendacan modifyTakes 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.
delete_agendacan modifyDeletes 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}.
Alternatives in Email & Messaging
Compare →
OpenPhone MCP by usefulapiB
Send and read OpenPhone messages, calls, contacts and phone numbers.
Missive MCP by usefulapiB
Read email/chat conversations, messages, contacts and teams; draft, send and update threads.
Loops MCP by usefulapiB
Manage Loops contacts, mailing lists, and transactional/event emails.
HelpCrunch MCP by usefulapiB
Manage HelpCrunch chats, customers, agents and knowledge-base articles.
Groove MCP by usefulapiB
Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.
Formbricks MCP by usefulapiB
Read survey responses and manage contacts, webhooks, teams and organisation users.