BriefGate MCP server

BriefGate

Client intake — from your browser, or from your AI coding agent.

Your agent can build the website. BriefGate gets the missing things from the client.

No agent? You don't need one. Everything below can be done by hand at app.briefgate.dev: build the request, send the link, watch answers arrive, download the results as one ZIP — no code, no API key, no MCP client. This package is for the other way of working, where an agent does it for you. See the dashboard quickstart.

Claude Code / Cursor / Codex → BriefGate → Client portal
  → Files · copy · credentials · structured data → Agent continues building

Watch as MP4 (25 s) · Full 47 s walkthrough

Website · MCP reference · llms.txt · Guides and checklists

The problem

Agents are fast. The bottleneck is the human on the other side of the project.

Somewhere in the middle of building, the agent needs something only the client has: a logo, homepage copy, brand colors, opening hours, hosting credentials, an API key, a piece of structured data like a price list. None of that exists in the chat, and none of it can be guessed.

The usual move is to stop and ask the developer to go chase the client by email. Instead, the agent creates a BriefGate intake. BriefGate emails the client, collects what comes back, chases automatically when it doesn't, and returns typed results the agent can use directly. The agent keeps building in the meantime.

Quickstart

Claude Code — hosted, no key to manage:

claude mcp add --transport http briefgate https://mcp.briefgate.dev/mcp

Then run /mcp in Claude Code, pick briefgate, and choose Authenticate.

Claude Code — local package:

claude mcp add briefgate -- npx -y @briefgate/mcp
npx -y @briefgate/mcp login

Prefer to skip sign-in entirely? Get a key at briefgate.dev (free tier, no card) and pass it as BRIEFGATEAPIKEY.

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "briefgate": {
      "command": "npx",
      "args": ["-y", "@briefgate/mcp"]
    }
  }
}

Then run npx -y @briefgate/mcp login, or ask the agent to call the login tool.

Codex:

codex mcp add briefgate --env BRIEFGATE_API_KEY=bg_live_xxxxx -- npx -y @briefgate/mcp

Gemini CLI — installs as an extension from this repo's gemini-extension.json, pointed at the hosted endpoint:

gemini extensions install https://github.com/sekera-radim/briefgate-mcp

It authenticates the same way as the other hosted clients above — via OAuth, on first use. The extension also ships GEMINI.md, a context file that tells the model what BriefGate is and when to reach for it.

By default gemini extensions install fetches the repo's latest GitHub Release rather than the main branch; if that release predates the current gemini-extension.json and the command reports a missing configuration file, install from main directly instead: gemini extensions install --ref main https://github.com/sekera-radim/briefgate-mcp.

Shortened. The full README is on GitHub.