Audience: Internal Brevian users connecting their Brevian workspace to Claude (claude.ai web and the Claude desktop app).

Companion doc: See the Brevian MCP Server tech spec for architecture and auth details.

What you get

Once connected, Claude can call the Brevian tool surface directly in-chat — list_opportunities, get_opportunity, search_meetings, get_coaching_report, search_stakeholders, search_activities, search_crm, search_transcripts, search_structured, search_coaching. All tools are read-only in Phase 1 and scoped to your user/org/workspace.

Prerequisites

A Brevian account on the environment you intend to connect (typically app.brevian.ai).
A Claude plan that supports custom connectors: Pro, Max, Team, or Enterprise. (Free is limited to one custom connector.)
Browser access to both Brevian and Claude.

Step 1 — Mint a Brevian MCP Personal Access Token (PAT)

The PAT is the user-identity primitive Claude will bind to via OAuth. You mint it once in the webapp and keep it somewhere safe.

Sign in to Brevian at https://app.brevian.ai.
Navigate to https://app.brevian.ai/settings/mcp. (The path is intentionally hidden — there is no nav link yet.)
Click Create token. Give it a recognizable name (e.g. Claude Desktop — <your laptop>).
Copy the token value immediately. It is shown exactly once; subsequent views return metadata only.
Store it in 1Password / Keeper under your personal vault. Do not paste it into chat, a PR, or a shared doc.

One PAT per client is the recommended pattern — it makes revocation surgical. If you connect Claude on both desktop and web, mint two PATs.

Step 2a — Connect on claude.ai (web)