BranderUX MCP
Enables AI agents to manage BranderUX projects, including brand settings, custom elements, screens, and API keys, with access to verified SDK documentation.
README
BranderUX MCP
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 design partners — everyone else lands on the waiting list.
Tools
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
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
| Env | Default | Purpose |
|---|---|---|
BRANDER_API_BASE |
http://localhost:8080/api/v1 |
BranderUX API base |
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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。