MCP.Market

Branderux MCP server

online · 100% uptime
by branderux.com·com.branderux/mcp·v0.1.3

One message in, a full agentic application out: website and MCP app, live. Built from any AI client.

A100/100grade A
What users say
No reviews yet
Be the first
Safety scan
A100/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Branderux yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Branderux tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 215ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year; website matches verified namespace10/10
Overall 100/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Branderux compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
100/100
higher than 100% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
213 ms
faster than 65% of 30,027 servers

Install Branderux in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.branderux.com/mcp
Add to Cursor

What the publisher says

From the Branderux repository's README, as published. We do not edit it. Read it on GitHub

BranderUX MCP

BranderUX builds agentic applications, in minutes: describe a business and a real agent builds its full application, published as a website and an MCP app, with every screen generated live, per customer, per question. This server is how any MCP client (Claude, ChatGPT, Cursor, VS Code) builds and controls those applications.

This is the official BranderUX MCP server. It gives an AI agent real control over BranderUX projects, brand, custom elements, screens, API keys, plus the verified reference docs it needs to integrate the SDK correctly.

Connect: https://mcp.branderux.com/mcp · Docs: https://branderux.com/mcp

claude mcp add --transport http branderux https://mcp.branderux.com/mcp

No API keys: the first tool call opens your browser for a one-click BranderUX sign-in (OAuth 2.1 + PKCE, scoped and revocable). Access is currently limited to beta accounts, everyone else lands on the waiting list, and you'll get an email the moment your access opens. While you wait: try a live BranderUX-built app at nova.branderux.app.

Tools

Knowledge (no scopes needed, signing in is still required to reach the server): getstarted · readdoc · searchdocs · getintegration_snippet

Projects (projects:): whoami · listprojects · getproject · createproject · updatebrandsettings · updateprojectsettings · delete_project

Screens (projects:write): listscreens · getscreen · putscreen · deletescreen, reads fetch the project aggregate; writes are atomic per-screen (row-locked server merge: parallel saves of different screens are safe).

Custom elements (elements:): listelements · getelement · listelementversions · createelement · publishelementversion · previewelement · deleteelement, your agent writes the TSX; the server pre-flight validates it (compile + sandbox import allowlist + export contract) before publishing. In clients that support MCP Apps, createelement, publishelementversion and previewelement render the element LIVE in the panel, demo props applied, clicks showing the exact query they would send.

API keys (keys:manage): createapikey · listapikeys · setkeyorigins · revokeapikey

Hosted agent: upsertagentconfig · getagentconfig, give the project its own agent: persona, policies (language and clock, login, access, handoff, write consent), answer quality and budgets.

Business data: defineentity · listentities · seedrecords · updaterecord · listentityrecords, managed records or live store/API feeds; every entity becomes a query tool for the agent (add-only writes by default).

Connectors: setconnectorcredential · probe_api, vaulted credentials and a probe so tools are wired against the real API shape.

Skills: upsertskill · listskills · delete_skill, SKILL.md behavior packs that ride every conversation.

Home screen: sethomescreen, a designed first paint with live data bindings, zero model cost per visit.

Publish: publishsite · getsite, one call and the full application is live: a website for people, an MCP app for AI agents.

Playground (no project needed): generate_screen, renders a real branded, interactive screen in the panel with demo data, powered by the same published @brander/mcp-tools package customers install. Ask for a storefront, analytics or order-flow screen to see actual BranderUX output before building anything.

Every destructive tool requires an explicit confirm: true.

Local development

npm install
BRANDER_API_BASE=http://localhost:8080/api/v1 npm run dev   # http://localhost:3010/mcp

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Branderux: common questions

Is Branderux MCP server safe?
Yes, by our scan: it is graded A (100/100). Read the Branderux safety report
How do I install Branderux?
It runs remotely at mcp.branderux.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Branderux need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Branderux maintained?
The last commit was 23 days ago (2026-10-13). The latest release is v0.1.3.
Is Branderux up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Branderux compare with other MCP servers?
safety score 100/100 (higher than 100% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 213 ms (faster than 65% of 30,027 servers). Full comparison.