Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Branderux MCP
Overview
Description from the maker (original English)
One message in, a full agentic application out: website and MCP app, live. Built from any AI client.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.branderux.com/mcpRun this in your terminal
claude mcp add --transport http branderux https://mcp.branderux.com/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"branderux": {
"url": "https://mcp.branderux.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"branderux": {
"type": "http",
"url": "https://mcp.branderux.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.branderux.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain branderux.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32558 servers in this category
- Published to the registry more recently than 35% of the other 32558 servers in this category
- Basic checks equal to or better than 100% of the other 32558 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Branderux MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, FactLot
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
FactLot
by 9mp96ygnbk-alt
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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/mcpNo API keys: the first tool call opens your browser for a one-click BranderUX sign-in (OAuth 2.1 + PKCE, scoped and revocable). Anyone with a BranderUX account connects. See what it builds: nova.branderux.app and the five live examples on branderux.com.
Tools
Knowledge (no scopes needed, signing in is still required to reach the server): get_started · read_doc · search_docs · get_integration_snippet · list_templates · get_template. The widget snippet of get_integration_snippet is the one-line script tag for a plain website (Wix, WordPress, Shopify, static HTML), carrying data-preload="eager" and data-conversions="on" (new leads, bookings, orders and requests are reported to the tags already on the site). list_templates and get_template read the five reference builds as worked examples to adapt, never to copy.
Projects (projects:*), for the signed-in user (projects they own or manage): whoami · list_projects · get_project · create_project · update_brand_settings · update_project_settings · delete_project
Screens (projects:write): list_screens · get_screen · put_screen · delete_screen, reads fetch the project aggregate; writes are atomic per-screen (row-locked server merge: parallel saves of different screens are safe).
Custom elements (elements:*): list_elements · get_element · list_element_versions · create_element · publish_element_version · preview_element · delete_element, 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, create_element, publish_element_version and preview_element render the element LIVE in the panel, demo props applied, clicks showing the exact query they would send.
API keys (keys:manage): create_api_key · list_api_keys · set_key_origins · revoke_api_key
Hosted agent: upsert_agent_config · get_agent_config, give the project its own agent: persona, policies (language and clock, login, access, handoff, write consent), answer quality and budgets.
Business data: define_entity · list_entities · seed_records · update_record · list_entity_records, managed records or live store/API feeds; every entity becomes a query tool for the agent (add-only writes by default).
Owner data (projects:read to read, projects:write to change): query_records · aggregate_records · get_record · list_conversations · aggregate_conversations · get_conversation · list_visitors · get_stats · update_record_workflow · correct_record · add_record · record_opt_out · delete_record · reply_links · get_crm_status · send_record_to_crm, the owner's own AI reads the leads, bookings, orders and requests the hosted agent collects, with its conversations, signed-in visitors and numbers, and works them one record at a time: every change is logged on the record (a delete erases the record with its log), visitor text comes back marked as data, nothing is sent to a customer (reply_links prepares a draft the owner sends), and where customer data goes stays the owner's or a manager's choice in the app. The review-my-week prompt goes through the owner's week or month with these tools. The docs: read_doc owner-data.
Connectors: set_connector_credential · probe_api, vaulted credentials and a probe so tools are wired against the real API shape.
Skills: upsert_skill · list_skills · delete_skill, SKILL.md behavior packs that ride every conversation.
Home and fixed screens: set_home_screen · set_fixed_screens · list_fixed_screens · verify_canned_screens, a designed first paint and designed answers to the business's recurring questions, each replayed with live data bindings at zero model cost per visit; verify_canned_screens runs every binding the way serving does, so a screen is proven to replay before publish_site.
Publish: publish_site · get_site, 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 installBRANDER_API_BASE=http://localhost:8080/api/v1 npm run dev # http://localhost:3010/mcp
| Env | Default | Purpose |
|---|---|---|
BRANDER_API_BASE | http://localhost:8080/api/v1 | BranderUX API base |
BRANDER_APP_BASE | from BRANDER_API_BASE: https://dev.branderux.com for api-dev, https://branderux.com for api, else http://localhost:3000 | The BranderUX web app: playground links, canned-screen verification and query_records on a live catalog |
MCP_RESOURCE_URL | http://localhost:3010 | Public URL of this server (OAuth resource id) |
OAUTH_ISSUER_URL | = BRANDER_API_BASE | Authorization server issuer |
The server is stateless: one MCP server instance per request, bound to the caller's bearer. Deploy target is Vercel (api/mcp.ts + api/oauth-protected-resource.ts).
License
MIT