upladsHelp CenterLogin

How to connect Claude or ChatGPT to uplads (MCP)

Last updated August 16, 2026

uplads runs an MCP server - a standard connection that lets an AI assistant work inside your workspace. Once it is connected, you describe the campaign you want in plain language and your assistant does the setup: it imports the creatives, writes the ad copy, creates the campaign and ad sets, and stages the launch for you to review.

MCP (Model Context Protocol) is the same open standard Claude, ChatGPT, Cursor and Claude Code use for every other connector, so there is nothing uplads-specific to install.

Where the connector lives

  1. Open Configuration from the left-hand navigation.
  2. Select the MCP section. You will see three cards: AI assistant, What your assistant can do, and Autonomous launching.
  3. The Connector URL at the top of the first card is what every client needs:
https://uplads.com/api/mcp

The connector is open to every workspace, so the MCP section is there for everyone. If you cannot see it, you are looking at a different section - it sits under Configuration → MCP.

Connect Claude or ChatGPT (no token needed)

Claude and ChatGPT sign in to uplads directly, so there is no key to copy anywhere.

Claude (claude.ai or the desktop app):

  1. Open Settings → Connectors.
  2. Add a custom connector, name it uplads, and paste the connector URL.
  3. Click Connect and sign in with your uplads account.
  4. Approve the consent screen.

ChatGPT:

  1. Open Settings → Connectors.
  2. Add a connector and paste the same URL.
  3. Authorize with your uplads account when prompted.

Custom connectors are only available on ChatGPT plans that allow them. If you do not see the option to add one, that is a plan restriction on ChatGPT's side, not a uplads setting.

Connect Claude Code, Cursor, VS Code or Codex

Developer clients authenticate with a personal access token instead of a sign-in.

  1. In the AI assistant card, expand Access tokens.
  2. Give the token a name that says where it lives, for example Claude Code on my laptop.
  3. Create it and copy the token immediately - only its hash is stored, so it is shown exactly once. If you lose it, revoke it and create a new one.
  4. Paste it into your client's MCP config. The Setup tabs in the same card generate the right snippet for each client; for Claude Code it is:
claude mcp add --transport http uplads https://uplads.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

Cursor, VS Code and Codex CLI use a config file - copy the snippet from the matching tab rather than typing it out. Any other client that speaks Streamable HTTP with a custom header works too.

Confirm the connection worked

The AI assistant card shows a green Connected badge (with the client's name for sign-in clients) once a client has actually reached your workspace. The simplest live check is to ask your assistant:

Which ad accounts do I have in uplads?

If it comes back with your account list, the connection is good.

Which workspace and permissions the assistant gets

The connection is scoped to your uplads account, which means:

  • It sees the ad accounts you can see, and nothing from other workspaces.
  • Every write passes the same permission and plan checks as the app. If your role cannot create campaigns, neither can your assistant.
  • Everything it does is written to your audit log, marked as coming from MCP.

Revoke access

Two places, depending on how the client connected:

  • Connected apps - clients that signed in (Claude, ChatGPT). Click Revoke on the row.
  • Access tokens - clients using a token. Click Revoke on the token.

Revoking takes effect immediately. You can also revoke from Claude's or ChatGPT's own connector settings; doing it in uplads is the one that definitely cuts access.

Which platforms MCP covers

Meta (Facebook and Instagram) today, including campaign and ad set creation with budgets, schedules, pixel selection and geo targeting. TikTok, Google Ads and Snapchat launching already exist in the uplads UI; MCP support for them follows.

Troubleshooting

Preparing works, creating does not. A workspace whose trial ended without a plan turns read-only, exactly as the interface does. Your assistant can still read the account; creating campaigns, importing creatives and staging drafts need an active plan.

Claude connects but does not see the new tools. Clients cache the tool list. Disconnect and reconnect the connector after uplads ships new tools.

"Daily MCP limit reached". The MCP surface has daily budgets for entity writes, drafts and imports - generous tripwires against a runaway agent, not a throttle for real work. They reset within a few hours; in the meantime you can carry on in the uplads UI. Do not have the assistant retry.

A token stopped working. Tokens are revoked, not expired. Check the Access tokens list - if it is gone, someone revoked it. Create a new one.

Related articles

Related articles