Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@BranderUX MCP Update the brand colors for my project Acme"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BranderUX is AI-UX infrastructure. Turn your agent into full agentic applications, websites and MCP apps — in minutes.
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). Access is currently limited to design partners — everyone else lands on the waiting list.
Knowledge (no scopes needed — signing in is still required to reach the server):
get_started · read_doc · search_docs · get_integration_snippet
Projects (projects:*): 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 — custom screens live on the project aggregate; these tools do the
read-modify-write for you.
Custom elements (elements:*): list_elements · get_element · 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
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.
Related MCP server: BrandKity MCP Server
npm install
BRANDER_API_BASE=http://localhost:8080/api/v1 npm run dev # http://localhost:3010/mcpEnv | Default | Purpose |
|
| BranderUX API base |
|
| Public URL of this server (OAuth resource id) |
| = | 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).
MIT
This server cannot be installed
SEO research, audits, backlinks, GSC, and content workflow tools for AI agents.
Project management for teams and their AI agents.
Manage SRG+ hubs, channels, content, assets, users, and workspaces from any MCP-aware AI agent.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BranderUX/branderux-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server