BriefMe

Official7 tools

by briefme

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

MCP Server: us.briefme/agenda-timer

The us.briefme/agenda-timer MCP server provides a meeting agenda timer for AI assistants. It is designed to help build agendas in chat and to share a live synced countdown. The server includes 7 tools to support these capabilities, as described in its repository metadata.

🛠️ Key Features

Meeting agenda timer for AI assistants
Build agendas in chat
Share a live synced countdown
7 tools

🚀 Use Cases

Running timed segments during meetings
Creating an agenda within a chat-based workflow
Keeping participants aligned with a live countdown

⚡ Developer Benefits

Tool-based MCP integration (7 tools)
Agenda timer functionality suitable for assistant-driven meetings

⚠️ Limitations

Available information only specifies agenda creation in chat and a live synced countdown; no further capabilities are described.

Captured live from the server via tools/list.

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.

Parameters3

title	string	required	Short name for the meeting, e.g. "Weekly engineering sync".
blocks	array	required	The agenda blocks, in the order they will run.
language	string	optional	The user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English.

Raw schema

{
  "type": "object",
  "properties": {
    "title": {
      "description": "Short name for the meeting, e.g. \"Weekly engineering sync\".",
      "maxLength": 120,
      "type": "string"
    },
    "blocks": {
      "description": "The agenda blocks, in the order they will run.",
      "minItems": 1,
      "maxItems": 40,
      "items": {
        "properties": {
          "title": {
            "description": "Short, active, scannable on a countdown screen.",
            "maxLength": 80,
            "type": "string"
          },
          "duration_seconds": {
            "description": "How long this block runs, in seconds.",
            "minimum": 30,
            "maximum": 14400,
            "type": "integer"
          },
          "block_type": {
            "description": "Internal classification for analysis — infer it from the content; never mention it to the user.",
            "enum": [
              "standup",
              "discussion",
              "decision",
              "q_and_a",
              "break",
              "opening",
              "closing",
              "other"
            ],
            "type": "string"
          },
          "description": {
            "description": "Optional one-line note, only when the title is ambiguous.",
            "maxLength": 280,
            "type": "string"
          }
        },
        "type": "object",
        "required": [
          "title",
          "duration_seconds",
          "block_type"
        ]
      },
      "type": "array"
    },
    "language": {
      "description": "The user's conversation language as a two-letter ISO 639-1 code (e.g. 'de'). Localizes the standard block titles quoted in structure_suggestions. Unsupported values fall back to English.",
      "type": "string"
    }
  },
  "required": [
    "title",
    "blocks"
  ]
}

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.

Parameters1

edit_token

string

required

The edit_token returned by create_agenda.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    }
  },
  "required": [
    "edit_token"
  ]
}

update_agenda

Changes the agenda's title. Does not touch any block — use the block tools for those. Returns the full updated agenda.

Parameters2

edit_token	string	required	The edit_token returned by create_agenda.
title	string	required	The new meeting title.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    },
    "title": {
      "description": "The new meeting title.",
      "maxLength": 120,
      "type": "string"
    }
  },
  "required": [
    "edit_token",
    "title"
  ]
}

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.

Parameters6

edit_token	string	required	The edit_token returned by create_agenda.
title	string	required	Short, active, scannable on a countdown screen.
duration_seconds	integer	required	How long this block runs, in seconds.
block_type	string	required	Internal classification for analysis — infer it from the content; never mention it to the user.
description	string	optional	Optional one-line note, only when the title is ambiguous.
after_block_id	string	optional	Insert directly after this block id. Omit to append to the end.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    },
    "title": {
      "description": "Short, active, scannable on a countdown screen.",
      "maxLength": 80,
      "type": "string"
    },
    "duration_seconds": {
      "description": "How long this block runs, in seconds.",
      "minimum": 30,
      "maximum": 14400,
      "type": "integer"
    },
    "block_type": {
      "description": "Internal classification for analysis — infer it from the content; never mention it to the user.",
      "enum": [
        "standup",
        "discussion",
        "decision",
        "q_and_a",
        "break",
        "opening",
        "closing",
        "other"
      ],
      "type": "string"
    },
    "description": {
      "description": "Optional one-line note, only when the title is ambiguous.",
      "maxLength": 280,
      "type": "string"
    },
    "after_block_id": {
      "description": "Insert directly after this block id. Omit to append to the end.",
      "type": "string"
    }
  },
  "required": [
    "edit_token",
    "title",
    "duration_seconds",
    "block_type"
  ]
}

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.

Parameters6

edit_token	string	required	The edit_token returned by create_agenda.
block_id	string	required	The id of the block to change, from create_agenda or get_agenda.
title	string	optional	New title. Omit to leave unchanged.
duration_seconds	integer	optional	New duration in seconds. Omit to leave unchanged.
block_type	string	optional	New internal classification. Omit to leave unchanged; never mention it to the user.
description	string \| null	optional	New note. Send null to clear it. Omit to leave unchanged.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    },
    "block_id": {
      "description": "The id of the block to change, from create_agenda or get_agenda.",
      "type": "string"
    },
    "title": {
      "description": "New title. Omit to leave unchanged.",
      "maxLength": 80,
      "type": "string"
    },
    "duration_seconds": {
      "description": "New duration in seconds. Omit to leave unchanged.",
      "minimum": 30,
      "maximum": 14400,
      "type": "integer"
    },
    "block_type": {
      "description": "New internal classification. Omit to leave unchanged; never mention it to the user.",
      "enum": [
        "standup",
        "discussion",
        "decision",
        "q_and_a",
        "break",
        "opening",
        "closing",
        "other"
      ],
      "type": "string"
    },
    "description": {
      "description": "New note. Send null to clear it. Omit to leave unchanged.",
      "maxLength": 280,
      "type": [
        "string",
        "null"
      ]
    }
  },
  "required": [
    "edit_token",
    "block_id"
  ]
}

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.

Parameters2

edit_token	string	required	The edit_token returned by create_agenda.
block_id	string	required	The id of the block to remove.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    },
    "block_id": {
      "description": "The id of the block to remove.",
      "type": "string"
    }
  },
  "required": [
    "edit_token",
    "block_id"
  ]
}

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.

Parameters2

edit_token	string	required	The edit_token returned by create_agenda.
block_ids	array	required	Every current block id, exactly once, in the order you want them to run.

Raw schema

{
  "type": "object",
  "properties": {
    "edit_token": {
      "description": "The edit_token returned by create_agenda.",
      "type": "string"
    },
    "block_ids": {
      "description": "Every current block id, exactly once, in the order you want them to run.",
      "minItems": 1,
      "items": {
        "type": "string"
      },
      "type": "array"
    }
  },
  "required": [
    "edit_token",
    "block_ids"
  ]
}

Install

Tools (7)

create_agendaget_agendaupdate_agendaadd_blockupdate_blockremove_blockreorder_blocks

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://briefme.us/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "agenda-timer": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://briefme.us/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

MCP Server: us.briefme/agenda-timer

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

create_agenda

get_agenda

update_agenda

add_block

update_block

remove_block

reorder_blocks

Install

Remote endpoint

Related servers