Client Intake for claude.ai: Ask the Client From a Browser
claude.ai connects to BriefGate as a custom connector — no install, no API key to copy, sign in once from your browser.
The problem
Not every project conversation happens in a coding agent. A lot of client work — reviewing a brief, drafting copy, planning a page — happens in a plain claude.ai chat, and it hits the same bottleneck: the client's logo or their hosting login lives in an inbox nobody in the conversation can reach.
Adding the connector
Individual Pro and Max accounts: go to Customize → Connectors, click +, choose Add custom connector, and enter:
- Name: BriefGate
- URL:
https://mcp.briefgate.dev/mcp
Leave Advanced settings (OAuth Client ID/Secret) blank. BriefGate's hosted endpoint supports OAuth 2.1 with PKCE and RFC 7591 dynamic client registration, so claude.ai registers itself automatically and walks you through sign-in and consent on the BriefGate dashboard — nothing to paste. The Free plan allows one custom connector; Pro and Max have no fixed limit documented by Anthropic as of this writing.
Team and Enterprise: an organization owner adds it once under Organization settings → Connectors → Add → Custom → Web with the same URL; members then turn it on individually from Customize → Connectors in their own chats, without repeating the setup.
Once added, enable BriefGate per conversation with the + button in the composer → Connectors.
What this gets you
All 13 tools become callable: define_intake, get_intake_status, get_intake_results, add_items, update_item, update_intake, list_intakes, request_revision, send_chase, manage_recipients, manage_webhook, list_folders, create_folder — see the MCP reference for full parameters.
A worked example
You: "Set up a BriefGate request for the Dvořák rebrand: the old logo files, the new tagline copy, and access to their Google Business Profile."
Claude calls define_intake with a file_list, a longtext, and a secret item. BriefGate emails the client a portal link and chases them on the schedule you set; come back to the same conversation later (or a new one) and ask Claude to check get_intake_status.
Handling the results
get_intake_results returns typed values once the client has submitted everything: files as signed URLs, text as plain strings, credentials decrypted and released exactly once. A missing array names anything still outstanding.
Next steps
- MCP tools reference — full parameter list for all 13 tools
- Item types — what each item type validates
- Claude Desktop setup — the same connector, plus a local-install option
- Quickstart — the same hosted endpoint for Claude Code, Cursor, or any other MCP client