BriefGate With AI Assistants
BriefGate is one MCP server — https://mcp.briefgate.dev/mcp, plus the local npx -y @briefgate/mcp package — that works the same way across every MCP-capable AI assistant: the assistant defines what it needs from a client, BriefGate emails them a portal link and chases them automatically, and the assistant retrieves typed results when the client is done. This page links the setup guide for each client and says plainly what is confirmed working and what isn't.
Setup guides by client
| Client | Transport | Auth | Status | Guide |
|---|---|---|---|---|
| Claude Code | Hosted HTTP or local npx |
OAuth (auto) or API key / device login | Confirmed working | Guide |
| Cursor | Hosted HTTP or local npx |
OAuth (auto) or API key | Confirmed working | Guide |
| OpenAI Codex (CLI, IDE extension, ChatGPT desktop app) | Hosted HTTP or local npx |
OAuth or API key | Confirmed working | Guide |
| claude.ai (web) | Hosted HTTP, custom connector | OAuth (auto, dynamic client registration) | Confirmed working | Guide |
| Claude Desktop | Hosted HTTP (connector) or local npx |
OAuth (auto) or API key / device login | Confirmed working | Guide |
| VS Code / GitHub Copilot | Hosted HTTP or local npx |
OAuth (auto, via VS Code's MCP client) or API key | Confirmed working | Guide |
| Gemini CLI | Hosted HTTP or local npx |
OAuth (auto discovery) or API key | Config confirmed against official docs; not run end-to-end by us | Guide |
| ChatGPT (Developer mode) | Hosted HTTP, custom connector | OAuth (auto, dynamic client registration) | Config confirmed against official docs; not run end-to-end by us | Guide |
| Windsurf (Cascade / Devin Desktop) | Hosted HTTP | API key header (confirmed); OAuth documented but exact config not confirmed | Header-based config confirmed; OAuth not confirmed | Guide |
"Confirmed working" means we've either connected it ourselves or the exact configuration is already documented and in production use. Where a row says "not run end-to-end by us," the configuration matches the client's own official documentation and BriefGate's OAuth implementation (OAuth 2.1, PKCE, RFC 7591 dynamic client registration — the same mechanism behind every "OAuth (auto)" row in this table), but we haven't personally walked through that specific client's login screen to confirm it. Each guide says so again at the point it matters, and gives you the fallback (usually an API key) if the automatic flow doesn't work for you.
Why one server works everywhere
BriefGate's hosted endpoint speaks the Model Context Protocol over Streamable HTTP and publishes standard OAuth 2.1 discovery metadata (/.well-known/oauth-authorization-server) with dynamic client registration and PKCE — any client that implements the MCP authorization spec can register itself and connect without a manually issued client ID. Clients that would rather not do a browser redirect (CI, scripts, or a client without OAuth support) can use a plain Authorization: Bearer header with an API key from https://app.briefgate.dev/app instead — every guide above documents both.
All 13 tools — define_intake, add_items, update_item, update_intake, list_intakes, get_intake_status, get_intake_results, request_revision, send_chase, manage_recipients, manage_webhook, list_folders, create_folder — are identical across every client, and map 1:1 to the REST API for anything that isn't MCP at all.
Not an agent-only tool
Everything above is for the moments an AI assistant is doing the asking. A person can do the exact same thing by hand, with no agent and no API key, from the dashboard quickstart — the client sees the same portal either way.
Pricing for agent users
Promotion code AGENT20 gives 20% off subscription invoices for the first 3 months (on annual billing: 20% off the first annual payment). It is entered on the Stripe Checkout page. Plans and limits: Billing and Plans.
Next steps
- MCP tools reference — full parameter list for all 13 tools
- Item types — what each item type validates, including
secret - Quickstart — the shortest path to a first working connection