BriefMe MCP MCP server

BriefMe is an official remote MCP server that allows AI assistants to create, manage, and share timed meeting agendas. It enables agents to build agendas from chat descriptions, list existing agendas, update blocks, and retrieve share links for synchronized countdowns across devices without requiring user signup for basic features.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by BriefMe

MCP endpoint (Streamable HTTP)

https://briefme.us/mcp

Vendor documentation

What you can do with it

Create a timed meeting agenda from a chat description
List agendas saved to a signed-in account
Update block titles, durations, or descriptions
Retrieve public share links for live countdowns

Tools advertised by the last live check:

create_agenda
list_agendas
get_agenda
get_shared_agenda
update_agenda
add_block
update_block
remove_block
reorder_blocks
rotate_edit_token
release_agenda
delete_agenda

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add briefme-mcp --url https://briefme.us/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable briefme-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "briefme-mcp": {
      "type": "streamableHttp",
      "url": "https://briefme.us/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start briefme-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "briefme-mcp": {
      "serverUrl": "https://briefme.us/mcp"
    }
  }
}

See all 1,687

Do you run BriefMe MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing