# BriefGate [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/sekera-radim/briefgate-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/briefgate

## Description
Your coding agent asks the client for logos, copy and credentials; BriefGate chases them for you.

## Tools
Capabilities this server exposes over MCP:

- **define_intake** — Create a new client intake — a branded portal where the client submits the assets you need. BriefGate sends the invite email and chases the client automatically until everything is collected.
- **get_intake_status** — Check which items are submitted, pending, or need revision. Includes the history of automated chase emails and when the client last opened the portal.
- **get_intake_results** — Retrieve typed submitted values. Files are signed URLs (valid 24 hours). **Secrets are one-time** — decrypted and returned on the first call only; store them before moving on.
- **request_revision** — Ask the client to resubmit an item with a note explaining what is wrong.
- **send_chase** — Send a manual reminder outside the automatic schedule. Use when a deadline is approaching or email attempts have failed.
- **list_intakes** — List all intakes across projects, optionally filtered by status, client email, folder, or a text search.
- **add_items** — Add new items to an already-sent intake — for example a favicon you forgot, or additional credentials needed mid-project.
- **update_item** — Change an item's definition after the intake was sent — the type, label, help text or constraints. Use this when you asked for the wrong thing, e.g. you requested an image but the client has a PDF.
- **update_intake** — Change settings on an already-sent intake — project name, due date, reminder cadence, quiet hours, the client brief, or the client's name, phone, language, and timezone. Use this instead of deleting and recreating the intake, which would re-send the invite.
- **manage_recipients** — Add, remove, or reinstate a person who receives an intake's invite and reminders, alongside or instead of the primary client.
- **manage_webhook** — Register, list or remove a webhook endpoint so events are pushed to your service instead of you polling.
- **list_folders** — List the folders in your account, used to group intakes by client or project. Takes no arguments.
- **create_folder** — Create a new folder to group intakes, e.g. one per client.
- **login** — Sign in without an API key — see [Sign in without an API key](#sign-in-without-an-api-key). Takes no arguments.
- **logout** — Removes the API key `login` stored locally for this BriefGate server, and best-effort revokes it on the server too. Takes no arguments.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/briefgate/readme_