UX Pilot

UX Pilot MCP

Design, edit and review in UX Pilot from Claude, ChatGPT, Cursor, Codex, and other MCP clients.

Your AI builds screens live on the UX Pilot canvas, or hands the brief to UX Pilot's own design agent. Then it reviews, versions and ships the work: React prototypes, preview links, videos and media.

---

The UX Pilot MCP server connects any MCP-compatible AI client to your UX Pilot workspace. Version 3.0 has 15 general tools. Each one covers a kind of work (find, read, edit, review, export and so on), and you choose the action inside the tool. That keeps the tool list short and leaves more of your AI's context for the work.

The server is hosted by UX Pilot. This repository documents how to connect to it and what it exposes. There is no server code here to build or run.

• Server URL: https://mcp.uxpilot.net/mcp
• Transport: Streamable HTTP (POST)
• Protocol: MCP 2025-11-25 (JSON-RPC 2.0)
• Auth: Native OAuth sign-in (recommended), or Authorization: Bearer API key fallback
• Tools: 15 (version 3.0)
• Free plan: connect with a free UX Pilot account and get 50 actions a week

What your AI can do

• Design on the canvas, live. Your AI places a screen as HTML, then builds it one section at a time while you watch it appear on the open canvas. Each step comes back with a picture of the result, and design checks point out problems with fixes.
• Run UX Pilot's design agent. Hand a brief to UX Pilot's own agent for screens, whole flows or a React app, on the standard, pro or ultra tier. Or mix the two: the agent drafts and your AI refines.
• Review. UX reviews, persona reviews, attention heatmaps and gaze flow, on a UX Pilot screen, raw HTML or a live URL. Heatmaps and gaze flow also take a screenshot. Fixes land as a new version.
• Make videos and media. Product reels, ads, explainers, social clips and logo animations, exported as MP4, WebM or GIF. Images, image edits, voiceovers, music and sound effects.
• Use your design system. Import one from code, a repository, a website or tokens, then design on brand with its guide.
• Ship. Turn screens into a React app, edit its files, publish it, or share a public preview link.
• Organize. Pages, folders, groups, versions, canvas notes, diagrams and comments.

Free plan

Free UX Pilot accounts can connect and use every tool:

• 50 actions a week that write or run something (imports, edits, organizing, designs, reviews, media, videos). Reading, searching, checking jobs and stopping runs are not counted. The week resets Monday 00:00 UTC.
• Design runs use the standard tier. Some features need a paid plan, the same as in the app. When one does, the tool says what is needed and links to the plans.
• AI runs spend credits, as they do in the app.

Paid plans have no weekly action limit. See uxpilot.ai/plans.

Authentication

Native sign-in (recommended)

If your AI tool shows a UX Pilot sign-in or authorization screen, choose that flow. You log in with your UX Pilot account, review the requested access, and approve the connection. No API key to copy or paste, and access stays tied to your account and plan.

API key fallback

For clients that only support static headers, generate a key from the API Keys tab in your UX Pilot workspace and send it as a bearer token:

Authorization: Bearer ep_your_api_key

Enterprise workspaces: your admin manages MCP/API keys. Keep the key private and rotate it if access changes.

Setup

Prefer native sign-in wherever the client supports it. Use the API key config as a fallback. Replace ep_your_api_key with your real key.

Claude

Native connector (recommended):

1. Open Claude settings, go to Connectors, and pick UX Pilot from the directory. Or add a custom connector with the server URL: https://mcp.uxpilot.net/mcp
2. Sign in with your UX Pilot account and approve access.
3. In a conversation, ask Claude to find your UX Pilot pages, or to design something on the canvas.

Claude Code:

claude mcp add --transport http uxpilot https://mcp.uxpilot.net/mcp

Then run /mcp in Claude Code and sign in.

API key fallback (Claude Desktop, via `mcp-remote`): edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json, Windows: %APPDATA%\Claude\claude_desktop_config.json)

{

"mcpServers": { "uxpilot": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.uxpilot.net/mcp", "--transport", "http-only", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer ep_your_api_key" } } } }

Requires Node.js. mcp-remote bridges stdio to Streamable HTTP.

ChatGPT

Use ChatGPT's custom connector / MCP support (Developer mode, availability depends on your plan):

1. Open ChatGPT settings and add a custom connector / MCP server.
2. Paste the server URL: https://mcp.uxpilot.net/mcp
3. Complete the UX Pilot sign-in when prompted.
4. Enable the connector in a chat and ask ChatGPT to find your UX Pilot pages.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). For native sign-in, add only the url. Keep the headers block only for the API key fallback.

{

"mcpServers": { "uxpilot": { "url": "https://mcp.uxpilot.net/mcp", "headers": { "Authorization": "Bearer ep_your_api_key" } } } }

VS Code + Copilot

Add to .vscode/mcp.json:

{

"servers": { "uxpilot": { "type": "http", "url": "https://mcp.uxpilot.net/mcp", "headers": { "Authorization": "Bearer ep_your_api_key" } } } }

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{

"mcpServers": { "uxpilot": { "serverUrl": "https://mcp.uxpilot.net/mcp", "headers": { "Authorization": "Bearer ep_your_api_key" } } } }

Codex

Add to ~/.codex/config.toml:

[mcp_servers.uxpilot]

url = "https://mcp.uxpilot.net/mcp" bearer_token_env_var = "UXPILOT_API_KEY"

Then export the raw key (no Bearer prefix; Codex adds it):

export UXPILOT_API_KEY="ep_your_api_key"

Any MCP client

Clients that do not speak Streamable HTTP can bridge through mcp-remote:

{

"mcpServers": { "uxpilot": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.uxpilot.net/mcp", "--transport", "http-only", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer ep_your_api_key" } } } }

Tools

15 tools. Most take a kind or action that picks what to do, and a params object with that action's fields. Ask the server with guide({ topic: " . " }), for example guide({ topic: "edit.patch" }), for an action's fields and an example.

Confirmation

Calls that spend credits, publish or delete stop and ask first:

1. The first call answers with a summary and a confirmationToken instead of running.
2. Your AI tells you what will happen and asks.
3. If you agree, it calls again with the same params plus confirmed: true and the token. The token is t