Use case

Your Cursor agent finished the build. Now it's waiting on the client.

The code is done. The homepage still has a placeholder logo and a login nobody has, and there's no way to fix either one inside the editor.

Try it free See what your client sees
The problem

Problem

Cursor's agent can scaffold, style, and wire up most of a client site in one session. Then it hits the same wall every time: the firm's logo file, the attorney bios for the About page, or the admin login for the case-management widget simply doesn't exist in the chat. Someone has to go get it from the client.

That "someone" is usually you, over email, days after the session ended:

  • You ask the agent to remind you to email the client — the reminder sits in a chat transcript nobody reopens.
  • The client replies with a phone photo of a logo, or forgets the second attachment, and you're manually tracking what's arrived across email and a shared drive.
  • A login gets typed into the chat in plain text, which is exactly where you don't want a client's password to live.
  • Two weeks later the project has stalled and there's no record of when you asked, or whether you asked twice.

The build was never the bottleneck. The gap between "I need this from the client" and having it, typed and usable, in the same session where you're building, is.

How it runs

Workflow

  1. Add BriefGate to Cursor. Point .cursor/mcp.json at the hosted https://mcp.briefgate.dev/mcp endpoint (sign in once via OAuth), or run it locally with npx -y @briefgate/mcp and a BRIEFGATE_API_KEY.
  2. The agent calls define_intake with the exact items it needs — a logo, bios, a login — instead of asking you to email the client.
  3. BriefGate emails the client a branded portal link. No account, no password on their end; the agent keeps building whatever doesn't depend on the missing items.
  4. The chase engine reminds automatically on the schedule you set, so a slow client doesn't require you to remember to follow up.
  5. A new Cursor session picks up where the last one left off — get_intake_status or list_intakes finds the same intake instead of the agent guessing or emailing the client a second link.
  6. Once the client is done, the agent calls get_intake_results and gets typed data and signed file URLs back — no re-asking, no guessing which file is the final one.
What your client sees
the branded page a client opens to upload files, answer questions and hand over logins
the branded page a client opens to upload files, answer questions and hand over logins
For the agent

MCP example

For a law office refresh, the agent asks for the logo, the attorney bios, a summary of practice areas, and the login for the case-management widget — the last one as a secret, not plain text:

{
  "project_name": "Ashford & Cole — Website Refresh",
  "client": {
    "email": "[email protected]",
    "name": "Maria Ashford",
    "language": "en"
  },
  "items": [
    {
      "key": "firm_logo",
      "type": "image",
      "label": "Firm logo",
      "required": true,
      "constraints": { "formats": ["svg", "png"], "min_width": 512 }
    },
    {
      "key": "attorney_bios",
      "type": "file_list",
      "label": "Attorney headshots and short bios",
      "required": true
    },
    {
      "key": "practice_areas",
      "type": "longtext",
      "label": "Practice areas summary",
      "required": true,
      "constraints": { "max_chars": 800 }
    },
    {
      "key": "case_mgmt_login",
      "type": "secret",
      "label": "Case management admin login",
      "required": true
    }
  ],
  "chase_schedule": "default"
}

get_intake_results hands the logo and bios back as signed URLs the agent can download directly, the practice-areas summary as a plain string, and the case-management login as a plaintext value revealed exactly once — sealed on BriefGate's server from the moment it arrived, never typed into the chat.

The secret item needs the Solo plan or higher; the other items in this example work on Free.

Read the docs

What changes

Result

  • The agent stops idling on a missing asset and keeps building around it instead.
  • Files, copy, and logins arrive already validated — the right format, the right length, no blurry phone photos to reject by hand.
  • A credential moves from client to codebase without ever sitting in plain text in an email or a chat transcript.
  • Every reminder and every submission is timestamped in the intake, so "did I already ask twice?" has an answer.

Add BriefGate to Cursor and send your next intake on the free tier — no card required.

Try it free See what your client sees

Free tier, no card required.