Docs · v1

Connect MakeUGC MCP

Use MakeUGC from Claude via the MCP server at https://mcp.makeugc.ai. You need a Platform API key and an active subscription.

Claude Code

Parameters

Transport is HTTP. Header name is X-API-Key. Place flags before the server name.

API key in config

cURL / CLI bash
claude mcp add --transport http makeugc https://mcp.makeugc.ai \
  --header "X-API-Key: YOUR_MAKEUGC_API_KEY"

claude mcp list

OAuth login

cURL / CLI bash
claude mcp add --transport http makeugc https://mcp.makeugc.ai
claude mcp login makeugc

Paste your Platform API key on the consent page, then approve. In session, /mcp should show makeugc as connected.

Claude Desktop / claude.ai

Parameters

  1. Open profile menu → Settings.
  2. Connectors → Add.
  3. Name the connector MakeUGC and set URL https://mcp.makeugc.ai.
  4. Connect, paste the Platform API key, and approve.
  5. In a chat, open + → Connectors and enable MakeUGC.

Claude Desktop via config file

Optional path if you skip Custom Connector. Edit claude_desktop_config.json, then fully quit and reopen Desktop.

JSON config

JSON json
{
  "mcpServers": {
    "makeugc": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.makeugc.ai",
        "--header",
        "X-API-Key:YOUR_MAKEUGC_API_KEY"
      ]
    }
  }
}

Verify and troubleshoot

  • /mcp failed — check the API key and that the subscription is active.
  • /mcp needs authentication — run claude mcp login makeugc.
  • 403 — renew the subscription on app.makeugc.ai.

Questions

What do I need before connecting MCP?

A Platform API key from Settings → API Integration and an active subscription. The MCP server is https://mcp.makeugc.ai.

Why does claude mcp add fail with an unknown flag?

Put --transport and --header before the server name. Do not put a raw url field in Claude Desktop config — use Custom Connector or the mcp-remote JSON shown here.