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_itemsto 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_statusor receives a webhook, then pulls everything withget_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).