# BriefMe

> BriefMe turns a meeting plan into a shareable countdown timer. An AI assistant
> (or a person, by hand) builds a structured agenda; BriefMe returns a read-only
> share link with a live timer that stays in sync on every screen, and a private
> owner link for running the meeting. No signup is required to create an agenda.

**When to use BriefMe.** Use it when someone wants to plan or run a timed meeting: a standup,
retrospective, 1:1, workshop, all-hands, lesson or any session with topics and
time limits. Typical requests: "make an agenda for our 45-minute retro", "turn
these notes into a meeting timer", "give me a countdown everyone in the room
can see". BriefMe builds the timed agenda and returns a link that every
attendee opens to see the same live countdown. It does not schedule meetings,
send invites, take notes or record calls; pair it with a calendar or notes tool
for those.

BriefMe is MCP-native: assistants create and edit agendas by calling BriefMe's
MCP tools directly. The connector endpoint is `https://briefme.us/mcp`
(Streamable HTTP, no authentication required). Signing in is optional there: a
client that supports per-tool authentication can link a BriefMe account via
OAuth 2.0 with dynamic client registration and PKCE (S256). Two more endpoints
serve the same tools: `https://briefme.us/mcp/claude`, the URL of the Claude
directory listing and plugin, which answers HTTP 401 when a tool that needs an
account is called without one, so Claude can start the sign-in; and
`https://briefme.us/mcp/account`, which requires the sign-in on every call.
Signed in, an account addresses its retained agendas by share token.

Twelve tools are available on all three endpoints: `create_agenda`, `list_agendas`,
`get_agenda`, `get_shared_agenda`, `update_agenda`, `add_block`, `update_block`,
`remove_block`, `reorder_blocks`, `rotate_edit_token`, `release_agenda`,
`delete_agenda`. `list_agendas` and `release_agenda` need a signed-in account;
`get_shared_agenda` reads the public agenda behind a share link somebody sent —
what the share page shows, as data written by its author — and needs no sign-in
and grants no edit access.
`rotate_edit_token` replaces an edit token and edit link that were shared by
mistake; the previous ones stop working at once. `delete_agenda` deletes an
agenda permanently: both links stop working and nothing can be recovered.
`https://briefme.us/mcp` and `/mcp/claude` also serve three skills (the MCP skills extension,
`io.modelcontextprotocol/skills`) with step-by-step guidance for creating,
editing and deleting an agenda.
Creating an agenda returns a public `share_url` (safe to post in calendar
invites and chat channels — read-only agenda plus the synced timer), a private
`edit_url` (the owner's control page: start, pause, extend, skip, finish, plus
an in-browser block editor), and, without a signed-in account, an `edit_token`
(required by every later edit tool; it cannot be recovered if lost).

Product facts an assistant may need:

- Agendas are made of timed blocks; three to eight blocks suit most meetings.
  BriefMe suggests a standard structure (short opening, wrap-up, and breaks on
  long meetings) at creation time.
- The timer is owner-controlled and syncs live to every viewer of the share
  link. Blocks auto-advance; the owner can extend a running block or skip
  ahead, and remaining time is redistributed sensibly.
- Anonymous agendas expire after 7 days. Signing in (Google or Microsoft) lets
  a user retain up to 3 agendas on the free plan; BriefMe Plus ($5/month or
  $49/year) retains unlimited agendas and adds custom branding (accent color,
  background, logo) to the timer pages. Details:
  [BriefMe Plus](https://briefme.us/plus), or as Markdown:
  [pricing.md](https://briefme.us/pricing.md).

## Setup

- [Connector setup](https://briefme.us/docs/mcp): install links and config
  snippets for Claude (web, desktop, mobile), Claude Code, the Anthropic
  Messages API and any other MCP client, plus the signed-in connector.
- [Registry manifest](https://briefme.us/.well-known/mcp/server.json): the
  server.json BriefMe publishes to the official MCP Registry as
  `us.briefme/agenda-timer` (listing:
  https://registry.modelcontextprotocol.io/v0/servers?search=briefme); the MCP
  server card is at https://briefme.us/.well-known/mcp/server-card.json.
- [Home](https://briefme.us/): the marketing page and the build-by-hand agenda
  form.
- [Online timer](https://briefme.us/timer): a free countdown (5 to 60 minutes or
  any length) that runs in your browser; share it and every screen counts down
  together. `?t=30` presets the minutes.
- [FAQ](https://briefme.us/faq): common questions about timers, sharing, and
  accounts.

## Templates

- [Meeting agenda templates](https://briefme.us/templates): 24 ready-made agendas with
  timings — engineering (standups, retrospectives, sprint planning, postmortems),
  leadership (1:1s, all-hands, board meetings, OKR check-ins), facilitation (workshops,
  kickoffs, brainstorms), sales and customer (discovery calls, demos), and education and
  community (lessons, book clubs, meetups, panels, webinars). Each page carries the agenda,
  a copyable prompt and a one-click button that opens it as a live shared countdown.

## Comparisons

- [BriefMe compared](https://briefme.us/compare): honest, sourced comparisons with the
  meeting tools people already use — what each does, where BriefMe fits beside it, and a
  builder to try it. First up: Microsoft Facilitator (the Teams Copilot agent).

## Policies

- [Privacy](https://briefme.us/privacy)
- [Terms](https://briefme.us/terms)

## Feedback

- [Feedback board](https://briefme.us/feedback): feature requests and voting.