BriefMe MCP server

• add_blockFree

  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.

• create_agendawrite actionFree

  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 edit_url (the private control page: start, pause, advance and finish the meeting, and edit blocks by hand), share_url (the read-only live timer for attendees, safe to post anywhere) and edit_token (needed by every other BriefMe tool, and the only way back into this agenda). 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. Agendas expire after 7 days and cannot be recovered afterwards.

• get_agendaFree

  Reads back the current state of an agenda, including the id of every block. Needed when block ids are unknown — typically at the start of a new conversation where the user has pasted an edit token; after any BriefMe mutation the current state is already in hand. Takes edit_token only. A share link or share URL does not open an agenda here: one known only by its share link cannot be read or edited through this connector, only re-created.

• remove_blockwrite actionFree

  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.

• reorder_blockswrite actionFree

  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.

• rotate_edit_tokenFree

  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 edit_token. The previous ones cannot be restored. Agendas expire after 7 days and cannot be recovered afterwards.

• update_agendawrite actionFree

  Renames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda.

• update_blockwrite actionFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 2961ms17/20
• Tool poisoning8 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

BriefMe: common questions

Is BriefMe MCP server safe?

With care: it is graded C, so read the findings first (56/100). Read the BriefMe safety report

How do I install BriefMe?

It runs remotely at briefme.us. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does BriefMe need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is BriefMe maintained?

The latest release is v1.0.0.

Is BriefMe up?

100% of our last 6 checks got an answer. We check remote servers about four times a day.

What can I use instead of BriefMe?

Servers from other publishers that do the same job: Vexa MCP server and Music Studio MCP server.