mcpbeat Sign in

BriefMe MCP Server

answering

BriefMe is answering right now. Last checked 7 min ago. It exposes 7 tools.

Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.

Uptime history 60 hours of history
60 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
352 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check BriefMe every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add agenda-timer --transport http https://briefme.us/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "agenda-timer": {
      "url": "https://briefme.us/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.agenda-timer]
url = "https://briefme.us/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agenda-timer": {
      "url": "https://briefme.us/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "agenda-timer": {
      "url": "https://briefme.us/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agenda
create_agenda
Creates a timed meeting agenda and returns the links that run it. Always reply to the user with BOTH links it returns. edit_url is the user's private control page — the only place the meeting can be started, paused, advanced and finished; a user who is not given it cannot run their meeting. It embeds the edit token on purpose: showing it to the user is required, and the one thing to avoid is posting it anywhere shared. The edit page also lets the owner add, change, remove and reorder blocks in the browser. share_url opens the read-only agenda with the live timer — safe to paste into an invite or a channel; attendees open it to follow along. edit_token is what every other BriefMe tool takes; keep it for the rest of the conversation, it is the only way back into this agenda. Durations: make the block durations add up to the meeting length the user asked for. If they did not give one, infer it — 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 countdown screen, so keep them to six words or fewer, active and scannable. Add a description only when the title alone is ambiguous. Structure every agenda by the rule below. Agendas expire after 7 days and cannot be recovered afterwards. - Open every agenda with a short welcome / check-in block ("Welcome & check-in", block_type opening): about 5% of the meeting, 1–10 minutes. End it with a wrap-up block for recap, next steps and good-byes ("Wrap-up & close", block_type closing): about 10% of the meeting, 2–15 minutes. Both count toward the meeting length. Only meetings under 10 minutes skip them. - Breaks ("Break", block_type break): none under 100 minutes; one from 100 minutes, two from 181, three from 271, four from 361, five from 451 — roughly one per 90 minutes of work, never leaving a stretch shorter than 45 minutes on either side. Each break is 10 minutes and comes out of the meeting length. Space them evenly and put each at the nearest block boundary: a 2-hour meeting gets one break at about 55 minutes. - For meetings of 5 hours or more, make the break nearest midday a 30–45-minute meal break if the start time makes that fit.
get_agenda
Reads back the current state of an agenda, including the id of every block. Use this when you need block ids you do not already have — for example at the start of a new conversation where the user has pasted an edit token. After any BriefMe mutation you already hold current state, so you do not need to call this again. Requires edit_token — a share link or share URL cannot be used here. If the user has only the share link, this agenda cannot be read or edited through this tool; tell them that and offer to create a new one instead.
update_agenda
Changes the agenda's title. Does not touch any block — use the block tools for those. Returns the full updated agenda.
block
add_block
Adds one block to an existing agenda. Appends it to the end, or inserts it directly after after_block_id when you supply one. Adds only — it does not reorder or change any existing block. Returns the full updated agenda, so you do not need to call get_agenda afterwards.
remove_block
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.
update_block
Changes one block, identified by block_id. Supply only the fields you want to change — anything you leave out keeps its current value exactly. Changes one block only: it does not reorder, add or remove anything. Do not re-send fields you are not changing, and do not rewrite the whole agenda to make one edit. If you do not have current block ids, call get_agenda first. Returns the full updated agenda.
reorder
reorder_blocks
Puts the agenda's blocks into the order you give. 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. If you are unsure of the current ids, call get_agenda first. Returns the full updated agenda.

Endpoints

URLTransportStateLatencyChecked
https://briefme.us/mcp streamable-http answering 374 ms 7 min ago

Alternatives to BriefMe

same job, measured the same way
A
Time
by b77

A live clock for your assistant.

answering
Agentschat MCP
by swswordholy-tech

Shared live rooms for AI agents to chat, vote, run OKRs, hand off to humans - join, don't rebuild.

178 installs/wk local only
Pocketlantern
by pocketlantern

Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.

51 installs/wk local only
C
Server4Agent
by server4agent

Give any MCP-compatible AI assistant a builder for live, hosted web tools and workflows.

answering
Roomcomm
by kotinder

Ephemeral REST chatrooms for AI agents to coordinate. Share a room URL — agents talk live.

11 tools answering
D
Whenly — group scheduling for AI agents
by workers-notdown-app-whenly

Agent creates a group-scheduling poll, gets a shareable link, and reads the best meeting time.

2 tools answering
Reachpad MCP
by reachpad

Coding agents build full-stack apps in persistent workspaces and share them by link.

11 tools answering
Open Zk Kb
by mrosnerr

Shared, persistent memory for AI assistants, built on the Zettelkasten method.

513 installs/wk local only

BriefMe — questions

Answers built from our own checks of this server.

What can BriefMe do?
It exposes 7 tools, read directly from the server on our last check. Among them: add_block, create_agenda, get_agenda, remove_block, reorder_blocks, update_agenda and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is BriefMe mostly used for?
Its tools cluster around block and agenda. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is BriefMe working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 352 ms. The bar chart above shows every period we have measured.
How do I connect BriefMe?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does BriefMe need an API key?
No. BriefMe completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is BriefMe?
It answers our handshake in 352 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.