Connector setup

One endpoint, every MCP client. Pick yours below, connect once, then describe a meeting in chat and the timed agenda appears.

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 with no authentication, it serves seven tools, and there is nothing to sign up for. 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:

Open Settings → Connectors in Claude.
Choose Add custom connector and name it BriefMe.
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"
        }
    }
}

Cursor and VS Code

Both editors accept an install link that adds the server for you. If you would rather edit the config file, the snippet under each button is the same thing.

Add to Cursor Add to VS Code

Cursor — ~/.cursor/mcp.json

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

VS Code — .vscode/mcp.json

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

Any other MCP client

Transport: Streamable HTTP (POST, JSON-RPC 2.0)
Authentication: None
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

A second endpoint, https://briefme.us/mcp/account, serves the same tools for a signed-in BriefMe account. It authenticates with OAuth 2.0 (dynamic client registration, PKCE), addresses agendas by their share token instead of an edit token, and retains them on the account — so a later conversation can find an agenda again, and it never expires. Add it exactly like the anonymous one 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, the private edit link and the edit token every later call needs.
get_agenda: Reads an agenda back by its edit token.
update_agenda: Renames an agenda; touches no block.
add_block: Appends one timed block.
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. Anonymous endpoint only.

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.