BriefGate – MCP server so your agent can request client assets (logo, copy, logins) and chase them

Sharing an MCP server I built for a very specific pain: Cursor finishes a client site in an afternoon, then the project waits two weeks for the logo, the copy and hosting access.

What it does

  • Your agent calls define_intake + add_items to list what it needs from the client (files, texts, choices, credentials).
  • The client gets a link to a no-account portal and uploads / fills things in.
  • BriefGate chases missing items automatically (scheduled reminders).
  • The agent polls get_intake_status or receives a webhook, then pulls everything with get_intake_results.
  • Credentials are encrypted at rest and released once; uploads are virus-scanned.

Setup in Cursor
Hosted endpoint (OAuth 2.1): mcp.briefgate.dev/mcp — add it as a url server in mcp.json.
Local: npx -y @briefgate/mcp login, then command npx, args -y @briefgate/mcp.
It is also listed on cursor.directory (search “BriefGate”) with a one-click “Add to Cursor”.

Free tier, no card. Docs: MCP Tools Reference — BriefGate Docs
Open-source client: GitHub - sekera-radim/briefgate-mcp: MCP server for BriefGate — your coding agent asks the client for logos, copy and credentials, and BriefGate chases them until they arrive. · GitHub

Happy to answer questions about the tool design (why the intake id and the portal token are separate, how chasing is scheduled).

Update: the first post was text-heavy, so here is the whole loop as a 27-second demo.

Your agent can write the site. The annoying part is still getting the logo, copy and credentials from the client. BriefGate lets the agent ask the client directly, and chases them until it arrives.

Demo: https://briefgate.dev/assets/demo/killer-demo.mp4

Setup for Cursor (and Claude Code / Codex): BriefGate for AI agents — let your agent ask the client