Log inSubmit server
BriefGate logo

BriefGate

Collects client files, text, structured data, and credentials through an MCP-managed intake workflow.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install BriefGate

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "briefgate": {
      "command": "npx",
      "args": [
        "-y",
        "@briefgate/mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

BriefGate MCP server lets coding agents request files, copy, structured data, and credentials from clients through a hosted portal. It emails an intake link, sends automatic reminders, and exposes typed responses, file URLs, and controlled secret retrieval through MCP tools. Use it when development is blocked on information held by someone outside the current conversation. It supports hosted and local setup, with authentication through OAuth-style login or a BRIEFGATE_API_KEY.

Use cases

  • Collect website assets and copy from a client
  • Request hosting or CMS credentials during development
  • Gather structured business data for an application
  • Track missing project inputs without manual email follow-up
  • Ask clients to correct unsuitable submissions

Key features

  • Branded client intake portals
  • Automatic and manual reminder emails
  • Typed results with signed file URLs
  • One-time secret retrieval
  • Webhook event delivery
  • Post-send intake and recipient management

Tools15

What BriefGate lets your agent do. Expand a tool for its parameters.

Self-reported~551 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @briefgate/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit12d agoMost recent push to the default branch.
Tools exposed15Callable tools this server registers over MCP.

How BriefGate works

What BriefGate MCP server does

BriefGate MCP server connects an AI coding agent with a client who needs to supply project materials. The agent defines an intake containing requested items, and BriefGate creates a branded client portal and sends the invitation email. Requested content can include files, text, choices, structured values, or secrets such as credentials.

The client does not need to provide information in the agent conversation. They use the emailed portal link instead. BriefGate tracks submissions, sends automatic reminders, and lets the agent continue work on parts of the project that do not depend on the missing inputs.

This fits client work such as websites and other projects where an agent needs a logo, images, copy, business details, social links, hosting access, or API credentials. It is intended for information that only an outside client, colleague, or customer can provide, not for details already available to the agent or the person currently using the chat.

How it works

The normal workflow starts with define_intake, which accepts a project, client details, and a list of items. Item definitions can include labels, types, constraints, and schemas. After the intake is sent, the agent can use get_intake_status to see what is complete, pending, or marked for revision. Status also includes reminder history and the client's latest portal access.

When the required material is available, get_intake_results returns typed values. Uploaded files are provided as signed URLs that remain valid for 24 hours. Secret items have a one-time reveal: the first results request returns the decrypted value, so the agent must store it before continuing. If an answer is unsuitable, request_revision sends the client a note asking for a replacement.

BriefGate MCP server also supports operational changes after delivery. An agent can add items, revise item definitions, change intake settings, manage recipients, send an immediate reminder, or register a webhook for pushed events rather than relying only on polling.

Setup and configuration

The hosted MCP endpoint can be added to Claude Code with an HTTP transport. A local installation uses the @briefgate/mcp package through npx. Local clients can authenticate by running the package's login tool or command. Alternatively, a BRIEFGATE_API_KEY can be supplied for key-based authentication. The logout tool removes the locally stored login key and attempts to revoke it remotely.

Cursor can configure the local package in .cursor/mcp.json. Codex can add the server with an environment variable, and Gemini CLI provides an extension installation from the repository that points to the hosted endpoint. Claude Desktop offers a Desktop Extension package running the local package. The repository also provides an Agent Skills-compatible collect-from-client skill, but the MCP server still needs to be configured separately.

Tools and capabilities

  • Create and send client intakes with define_intake.
  • Inspect progress and reminder activity with get_intake_status.
  • Retrieve typed answers, 24-hour file URLs, and one-time secrets with get_intake_results.
  • Request corrections with request_revision or send an unscheduled reminder with send_chase.
  • Find intakes using status, email, folder, or text filters through list_intakes.
  • Modify sent intakes and their items with add_items, update_item, and update_intake.
  • Add, remove, or reinstate intake recipients with manage_recipients.
  • Register, inspect, or remove webhook endpoints with manage_webhook.
  • Organize work with list_folders and create_folder.
  • Authenticate locally with login and logout.

Limitations and notes

File result URLs expire after 24 hours, so consumers should download or process files within that window. Secret values are returned only once; losing the first response requires handling the credential workflow carefully. A status showing that an intake is not ready represents an ordinary intermediate state while the client is still responding.

Updating an existing intake is preferable to deleting and recreating it when requirements change, because recreating it would send another invitation.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about BriefGate

BriefGate is an MCP server that connects coding agents to clients through intake portals. Its main tools create and manage requests, track submitted items, retrieve typed results and files, request revisions, send reminders, and handle one-time secret retrieval. It helps agents collect project assets, copy, structured data, and credentials from people outside the current conversation.

Install it locally with `npx -y @briefgate/mcp`, then configure that command in your MCP client. Claude Code can also use the hosted endpoint, while Gemini CLI and Claude Desktop provide repository-based or extension-based setup. Authenticate with the `login` tool or provide `BRIEFGATE_API_KEY`.

Yes, BriefGate works with Cursor through a `.cursor/mcp.json` configuration or the repository's Cursor plugin. The local configuration runs `npx -y @briefgate/mcp`; authenticate afterward with the login command or tool.

BriefGate returns secret items only on the first `get_intake_results` call. The value is decrypted for that response, so the agent must store it before making further progress.

Yes, use `add_items` to request more information, `update_item` to change an item's definition, or `update_intake` to change settings such as the due date, reminders, brief, or client details. Updating avoids sending a new invitation through deletion and recreation.

Related MCP servers

All in Coding Agents All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBriefGate AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/briefgate?style=directory)](https://allmcps.com/mcp/briefgate)
HTML Embed
<a href="https://allmcps.com/mcp/briefgate"><img src="https://allmcps.com/api/badge/briefgate?style=directory" alt="BriefGate on AllMCPs" /></a>