BranderUX MCP

What the BranderUX MCP MCP server does

The BranderUX MCP MCP server connects MCP clients to BranderUX, a platform that generates and publishes agentic applications as websites and MCP apps. After authentication, an agent can manage projects, brand and project settings, screens, custom elements, API keys, hosted-agent configuration, business records, skills, connectors, and fixed screens.

It also provides reference and integration tools. Agents can search and read BranderUX documentation, retrieve integration snippets, and inspect five reference templates. The widget integration snippet is intended for plain websites and platforms such as Wix, WordPress, Shopify, and static HTML.

How it works

The server is available at https://mcp.branderux.com/mcp and authenticates users through a browser sign-in flow using OAuth 2.1 and PKCE. The first tool call opens the browser; access is scoped and revocable, and the server does not require an API key for this connection.

Project operations apply to projects the signed-in user owns or manages. Screen writes are atomic per screen, while reads retrieve the project aggregate. Custom element code is written as TSX and checked before publication through compilation, a sandbox import allowlist, and an export contract. In MCP Apps-capable clients, element creation, preview, and publication can render a live panel view with demo props.

Destructive operations require confirm: true. The server is stateless, creating one MCP server instance per request and binding it to the caller's bearer token.

Setup and configuration

Add the hosted endpoint to Claude with:

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

The same endpoint is intended for MCP clients that support the HTTP transport. Local development uses npm install, followed by npm run dev; the local MCP endpoint is http://localhost:3010/mcp. The documented configuration variables are BRANDER_API_BASE, BRANDER_APP_BASE, MCP_RESOURCE_URL, and OAUTH_ISSUER_URL. Each has a documented default, including a local API base and local public resource URL.

Beta access is required. Users without access are sent to a waiting list and notified when access becomes available.

Tools and capabilities

The BranderUX MCP MCP server groups tools across several application areas:

• Knowledge tools for documentation, integration snippets, templates, and getting started.
• Project and screen tools for creating, updating, reading, and deleting application structure.
• Custom-element tools for creating, previewing, validating, versioning, publishing, and deleting TSX elements.
• Business-data tools for defining entities, seeding records, updating records, and querying owner data.
• Hosted-agent tools for persona, policy, answer-quality, and budget settings.
• Connector tools for storing vaulted credentials and probing an API's shape.
• Skills tools for managing SKILL.md behavior packs.
• Publishing tools for setting the home screen, configuring fixed screens, verifying canned screens, and publishing the site.

A playground tool can generate an interactive branded screen with demo data without an existing project. Published applications can serve both human visitors through a website and AI agents through an MCP app.

Limitations and notes

The BranderUX MCP MCP server is currently restricted to beta accounts. The README does not identify a separate API-key setup for the hosted MCP connection. Customer-facing replies are not sent directly by owner-data tools: reply_links prepares a draft for the owner to send. Destructive actions require explicit confirmation, and connector credentials are described as vaulted rather than exposed as ordinary configuration values.

The project is licensed under MIT.