How to connect Claude or ChatGPT to uplads (MCP)

Last updated October 2, 2026Auf Deutsch lesen

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. It also manages what already runs, on Meta, TikTok, Google Ads and Snapchat, and sets up rules, runs audits and keeps your media library in order.

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

Open Configuration from the left-hand navigation.
Select the MCP section. You will see three cards: AI assistant, What your assistant can do, and Autonomous launching.
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):

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

ChatGPT:

Open Settings → Connectors.
Add a connector and paste the same URL.
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 sign in the same way, with the same URL. There is no token to create.

In the AI assistant card, open the Setup tab for your client.
Copy the snippet into your client's MCP config. For Claude Code it is one command:

claude mcp add --transport http uplads https://uplads.com/api/mcp

Run /mcp in Claude Code, or start your client, and sign in with your uplads account when it asks.

Cursor, VS Code, Codex CLI and Antigravity use a config file. Copy the snippet from the matching tab rather than typing it out. Any other client that speaks Streamable HTTP 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

Every client that signed in is listed under Connected apps in the AI assistant card. Click Revoke on its row.

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.

Give your assistant the context file

An assistant that has never seen uplads works it out from the tool descriptions alone, which costs turns and sometimes leaves targeting half-done. We publish a context file that fixes that:

https://uplads.com/uplads-mcp.md

Save it as .claude/skills/uplads/SKILL.md in your project, paste it into your CLAUDE.md, or attach it to a Claude or ChatGPT conversation. The same URL is in the AI assistant card under Context file.

Which platforms MCP covers

All four networks uplads launches on. On each, your assistant builds paused structure, stages new ads as a launch draft for you to launch, and manages what already runs:

Meta (Facebook and Instagram) has the deepest reach: campaigns and ad sets with budgets, schedules, pixel selection and targeting, drafts with carousels, catalogs and several languages, changes to targeting, texts and creatives of running ads, Optimize audits, value rules, catalogs and partnership ads.
TikTok: campaigns and ad groups, drafts from your library or as a Spark Ad on your own posts, status, budgets, bids, names, captions, landing pages and copies, and automated rules.
Google Ads: paused Search, Display, Demand Gen, Performance Max and App campaigns, drafts for new asset groups, Demand Gen and YouTube ads, status, budgets, bidding, keywords, ad and asset group texts, reports and change history.
Snapchat: campaigns and ad sets, drafts for new Snap Ads, status, budgets, bids, names and copies.

How a draft works on each network is in What your AI assistant can do in uplads. The details for running campaigns are in What your AI assistant can change in running campaigns.

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 client stopped working. Check Connected apps. If the client is no longer listed, its access was revoked; connect it again and sign in.