Ads Uploader

What Ads Uploader MCP server does

Ads Uploader MCP server exposes Ads Uploader’s Meta advertising workflows through MCP. It connects to Meta ad accounts, Facebook Pages, and connected Instagram accounts, allowing an agent to inspect existing campaigns and ads, prepare reusable builds, upload creative assets, and submit new ad creation jobs.

The service can build ads from an existing ad’s configuration or from a saved build. New media, copy, calls to action, links, and targeting can be supplied for a launch. It also supports duplicating ads by Page post ID, which preserves the source post’s social proof such as likes, comments, and shares.

Partnership and branded-content workflows are included. Ads can use uploaded media with a selected partner identity, or an imported Instagram creator post. The available sponsorship and identity settings can be checked during preview before creation.

How it works

An agent first authenticates and discovers the available Meta accounts, campaigns, ad sets, ads, Pages, and Instagram connections. It can inspect an existing ad, search targeting values, and browse or save presets and builds. Saved builds provide a durable draft that can be edited, forked, or later launched from the Ads Uploader web application.

Media can be imported from public URLs, a Google Drive folder, or local files. Uploads may be handled as batches, with separate tools for finalizing presigned uploads and checking ingest status. Creation and ingestion run as jobs that can be polled, resumed, or cancelled.

The preview operation resolves a specification and checks Meta permissions and partnership sponsors without creating ads. This makes it suitable for a review step before submitting a bulk launch. The README recommends using saved builds when an agent-assisted workflow should leave final review and launch to a person in the web interface.

Setup and configuration

The hosted Ads Uploader MCP server is available at https://adsuploader.com/api/mcp. Claude Code can add it with the HTTP transport, and Claude Desktop, Claude.ai, ChatGPT, Cursor, Grok, and Codex have documented connection methods. Authentication takes place through a browser sign-in and consent flow.

Ads Uploader MCP server requires a paid Ads Uploader account with MCP access and a connected Meta account with the required permissions. MCP access is not included in trials. The README does not define environment variables for the hosted connection.

A local option is available for hosts that need to read files directly from disk. It requires Node.js 18 or newer, the @adsuploader/cli and @adsuploader/mcp packages, and an ads login step. The local MCP configuration runs the ads-mcp command and uses credentials saved by that login.

Tools and capabilities

• Inspect authentication, Meta accounts, campaigns, ad sets, ads, Pages, and connected Instagram accounts.
• Read creative details and search Meta targeting values.
• Browse, save, edit, fork, and delete reusable presets and builds.
• Upload media, finalize upload batches, and monitor ingest jobs.
• Preview specifications, create ads from specifications or builds, and cancel creation jobs.
• Duplicate ads by Page post ID or create partnership ads.

Limitations and notes

Ads Uploader MCP server is a connector to a proprietary product; this repository contains public documentation and configuration, not the application, backend, or MCP implementation. Successful use depends on the Ads Uploader subscription, MCP access, Meta account permissions, and any required partnership authorization.

The documented Grok connection is awaiting an end-to-end test. The README also distinguishes agent-assisted operation from fully headless launching and recommends a saved-build review process for polished launches. Use preview tools before creation when permission checks and effective partnership sponsors need to be verified.