UX Pilot

UX Pilot MCP

Work directly inside UX Pilot from Claude, ChatGPT, Cursor, Codex, and other MCP clients.

Bring AI-generated work into UX Pilot, organize it, review and version it, build prototypes, then switch back to UX Pilot AI for deeper product-aware generation.

The UX Pilot MCP server connects any MCP-compatible AI client to your UX Pilot workspace. Your assistant can create workstreams and pages, import HTML or live URLs as designs, run UX and accessibility reviews, manage versions and comments, and generate React prototypes, all inside UX Pilot.

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: 87

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 and add a custom connector / remote MCP server.
2. Paste the server URL: https://mcp.uxpilot.net/mcp
3. Choose the UX Pilot sign-in flow when Claude offers it and approve access.
4. In a conversation, ask Claude to list UX Pilot tools.

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 list UX Pilot tools.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). Adding the URL alone triggers native sign-in if supported; the header is 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

87 tools, grouped by what they do. Tools marked · credits consume account credits; credit-consuming and destructive actions require explicit confirmation.

Discover and inspect (13)

Organize your workspace (19)

Generate with UX Pilot AI (5)

Edit designs and React code yourself (7)

These edits run without UX Pilot AI and consume no credits.

Bring in external AI output (15)

Review, audit, and accessibility (10)

Versions and comments (12)

Prototype and publish (5)

Plus request_action_confirmation, a safety utility that mints a confirmation token for risky actions.

Quick start

1. Pick the AI client you want to use with UX Pilot.
2. Use the native sign-in steps above with the server URL.
3. If your client needs static headers, generate an API key and replace ep_your_api_key in the fallback config.
4. Ask your assistant: "Create a UX Pilot page, import this HTML as a design, then run a UX review."

Support

• Product and account help: uxpilot.ai
• Issues with this integration: open an issue
• MCP specification: modelcontextprotocol.io