BriefGate vs Clize
A side-by-side look at the BriefGate and Clize MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose BriefGate for coding agents work as a local process; choose Clize for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose BriefGate when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
define_intake, get_intake_status, get_intake_results.
Choose Clize when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
clize_status, clize_balance, clize_recharge.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 52/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 15 | 33 |
| Full listing | View BriefGate | View Clize |
Tools & capabilities
BriefGate tools 15
define_intakeCreate 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_statusCheck 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_resultsRetrieve 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_revisionAsk the client to resubmit an item with a note explaining what is wrong.send_chaseSend a manual reminder outside the automatic schedule. Use when a deadline is approaching or email attempts have failed.list_intakesList all intakes across projects, optionally filtered by status, client email, folder, or a text search.add_itemsAdd new items to an already-sent intake — for example a favicon you forgot, or additional credentials needed mid-project.update_itemChange 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_intakeChange 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_recipientsAdd, remove, or reinstate a person who receives an intake's invite and reminders, alongside or instead of the primary client.manage_webhookRegister, list or remove a webhook endpoint so events are pushed to your service instead of you polling.list_foldersList the folders in your account, used to group intakes by client or project. Takes no arguments.- +3 more on the listing page
Clize tools 33
clize_statusworkspace overview: domains / mailboxes / sites / this month's spend (only the project's when one is checked out)clize_balanceclize balance + recent ledger (hosted)clize_rechargetop up the clize balance (hosted): returns a Stripe payment link; give it to the user to pay in a browser, the balance updates automaticallyclize_paycharge your customers (hosted): create a payment link for an end customer. Zero configuration — the destination is chosen automatically by default: your own Stripe if connected (clize takes a fee), otherwise your clize balance (no fee, not withdrawable). action=connect only returns where to connect (the user must log in to Stripe on the web and complete KYC; an agent cannot); status shows connection / charge status; link creates a payment link (needs amountUsd, optional customerRef / purpose, mode defaults to auto; returns a checkoutUrl to send to the customer); list lists the links created.clize_domain_searchcheck domain availability + price (several queries allowed; one with a dot is a full domain, otherwise tld applies)clize_domain_buyregister a domain (💰 costs money: confirm=true required, otherwise only a quote — report it to the user first; belongs to the checked-out / project-specified project, or to a project named after the handle when none is checked out)clize_claimclaim a free handle <slug>.clize.app (first come, first served; the placeholder site is immediate; email=true also opens support@ inbound, off by default to save the shared zone's DNS quota, clize_email_setup can add it later; belongs to the checked-out / project-specified project, or to a project named after the handle when none is checked out). With email=true the call returns only once Cloudflare accepts mail for support@ (about 100 s; mail sent earlier is rejected and never retried); wait=false returns at once with inboundLiveAfterclize_domain_nsshow / set a domain's NS delegation. Without nameservers = show (registrar + current NS + target CF NS); with = set (a clize-registered Vercel domain can point to CF or away; CF-registered stays on CF; an external domain gets the values to set at its registrar). ⚠️ Pointing away from CF breaks the domain's clize mailboxes / site.clize_dns_listlist all DNS records of a domain on Cloudflare (A/CNAME/MX/TXT…; the NS must be on CF)clize_dns_setadd / change one DNS record (overwrites an existing record with the same type+name; the NS must be on CF)clize_dns_rmdelete one DNS record (located by type+name; idempotent)clize_email_setupset up send and receive on a domain and open its support@ inbox (custom domain: MX / SPF + sending verification + support@; free handle <slug>.clize.app: the support@ inbox); returns once Cloudflare accepts mail for a newly opened support@ (wait=false returns at once)- +21 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
BriefGate
{
"mcpServers": {
"briefgate": {
"command": "npx",
"args": [
"-y",
"@briefgate/mcp"
]
}
}
}
Clize
{
"mcpServers": {
"clize": {
"command": "npx",
"args": [
"-y",
"-p",
"@clize/clize",
"clize-mcp"
]
}
}
}
Frequently asked questions
BriefGate is categorized under Coding Agents and uses a local stdio subprocess. Clize belongs to Coding Agents and uses a local stdio subprocess. Pick BriefGate for coding agents work and Clize for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
BriefGate has no declared pricing — check the project's own site. Clize has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add briefgate and clize as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BriefGate has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Clize has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.