Connector setup

What this is

BriefMe turns a meeting plan into a shareable countdown timer. Agendas are created and edited entirely over MCP; no account is required. It is a remote MCP server over Streamable HTTP that serves twelve tools, needs no authentication and has nothing to sign up for. Signing in is optional: a linked BriefMe account keeps its agendas instead of letting them expire (see the signed-in connector below). The endpoint is https://briefme.us/mcp.

https://briefme.us/mcp

Claude (web, desktop, mobile)

One click opens Claude's connector settings with BriefMe already filled in — on the web, in the desktop app and on a phone alike.

Add to Claude

Or by hand:

1. Open Settings → Connectors in Claude.
2. Choose Add custom connector and name it BriefMe.
3. Paste https://briefme.us/mcp as the URL and save.

Claude Code

Run once in a terminal:

claude mcp add --transport http briefme https://briefme.us/mcp

Or commit it to the project's .mcp.json, so everyone working on the repository gets it:

{
    "mcpServers": {
        "briefme": {
            "type": "http",
            "url": "https://briefme.us/mcp"
        }
    }
}

Any other MCP client

Transport

Streamable HTTP (POST, JSON-RPC 2.0)

Authentication

None required (OAuth 2.0 optional, to link a BriefMe account)

Endpoint

https://briefme.us/mcp

From the Anthropic Messages API, send the beta header anthropic-beta: mcp-client-2025-11-20 and add this to the request body:

{
    "mcp_servers": [
        {
            "type": "url",
            "url": "https://briefme.us/mcp",
            "name": "briefme"
        }
    ],
    "tools": [
        {
            "type": "mcp_toolset",
            "mcp_server_name": "briefme"
        }
    ]
}

Signed-in connector

The endpoint above also takes an optional sign-in: a client that supports authentication per tool offers to link a BriefMe account when a tool needs one. A second endpoint, https://briefme.us/mcp/account, serves the same tools with sign-in required on every call, for clients that sign in when the connector is added. Both authenticate with OAuth 2.0 (dynamic client registration, PKCE). Signed in, agendas are addressed by their share token instead of an edit token and retained on the account — so a later conversation can find an agenda again, and it never expires. Add the second endpoint exactly like the first and follow the sign-in prompt your client shows.

What the tools do

create_agenda

Builds an agenda from a title and a list of timed blocks. Returns the public share link and the private edit link; without an account also the edit token every later call needs.

list_agendas

Lists the agendas saved to the signed-in account, newest first. Needs sign-in.

get_agenda

Reads an agenda back by its edit token, or by its share token when signed in.

get_shared_agenda

Reads the public agenda behind a share link somebody sent — title, blocks and timer status, exactly what the share page shows. Grants no edit access; the text comes back as data written by the agenda's author.

update_agenda

Renames an agenda; touches no block.

add_block

Adds one timed block at the end, keeping a wrap-up block last; after_block_id places it anywhere else.

update_block

Changes one block's title, duration or description; everything else stays as it was.

remove_block

Removes one block — an agenda always keeps at least one.

reorder_blocks

Sets the running order from the full list of block ids.

rotate_edit_token

Replaces the edit token and edit link; the previous ones stop working at once.

release_agenda

Takes a saved agenda out of the account; its share link keeps working for 7 days, then it expires. Needs sign-in.

delete_agenda

Deletes an agenda for good: both links stop working at once, and nothing can be recovered.

Support and policies

Something not connecting? Email support at briefme.us , or post it on the feedback board. What BriefMe stores and for how long is in the privacy policy; the terms of use cover the rest.