Connect BriefMe and your agent gets 8 tools, among them add_block, create_agenda, get_agenda. It answers at https://briefme.us/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Meeting agenda timer for AI assistants: build agendas in chat, share a live synced countdown.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_block | 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 afterw Inputs: edit_token, title, duration_seconds, block_type, description, after_block_id |
create_agenda | 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 t Inputs: title, blocks, language |
get_agenda | 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 sta Inputs: edit_token |
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 Inputs: edit_token, block_id |
reorder_blocks | 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 i Inputs: edit_token, block_ids |
rotate_edit_token | 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 mi Inputs: edit_token |
update_agenda | Renames the agenda. Blocks are untouched — the block tools change those. Returns the full updated agenda. Inputs: edit_token, title |
update_block | 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 Inputs: edit_token, block_id, title, duration_seconds, block_type, description |
Every block below points at https://briefme.us/mcp. Pick your client and copy.
claude mcp add --transport http briefme https://briefme.us/mcp
{
"mcpServers": {
"briefme": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://briefme.us/mcp"]
}
}
}{
"mcpServers": {
"briefme": {
"url": "https://briefme.us/mcp"
}
}
}{
"servers": {
"briefme": {
"type": "http",
"url": "https://briefme.us/mcp"
}
}
}{
"context_servers": {
"briefme": {
"url": "https://briefme.us/mcp"
}
}
}{
"mcpServers": {
"briefme": {
"serverUrl": "https://briefme.us/mcp"
}
}
}{
"mcpServers": {
"briefme": {
"url": "https://briefme.us/mcp"
}
}
}name: BriefMe
version: 0.0.1
schema: v1
mcpServers:
- name: BriefMe
type: streamable-http
url: https://briefme.us/mcp{
"mcpServers": {
"briefme": {
"httpUrl": "https://briefme.us/mcp"
}
}
}{
"mcpServers": {
"briefme": {
"type": "http",
"url": "https://briefme.us/mcp"
}
}
}{
"mcpServers": {
"briefme": {
"url": "https://briefme.us/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbriefme.us%2Fmcp&type=streamable_http&id=briefme&name=BriefMe
It answered our last check on 24 October 2026 in 239 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by briefme.us and served from briefme.us, the vendor's own domain: https://briefme.us/mcp.
8, as returned by the server's own tools/list on 23 September 2026: add_block, create_agenda, get_agenda, remove_block, reorder_blocks, rotate_edit_token, update_agenda, update_block.
It answered our last check on 24 October 2026 in 239 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://briefme.us/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: us.briefme. Endpoint host: briefme.us. ARD identifier: urn:air:us.briefme:mcp:agenda-timer.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.