Other · Remote MCP server

Ads Uploader

Meta ads bulk launcher: upload creatives, edit builds, preview, and create paused ads.

Visit Ads Uploader's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.adsuploader/mcp
Version
0.3.0
Status
Active
Category
other
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-21
Updated
2026-09-21
Publisher
com.adsuploader
Namespace
Namespace verified by the MCP Registry via the domain adsuploader.com · how
Website
adsuploader.com
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://adsuploader.com/api/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@adsuploader/mcp0.3.0stdioNone declared

How to connect Ads Uploader

Ads Uploader is a remote MCP server: there is nothing to install. Its endpoint is https://adsuploader.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @adsuploader/mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @adsuploader/mcp@0.3.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@adsuploader/mcp@0.3.0"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Adrex AIOpen-source MCP server for Google Ads & Meta Ads - manage campaigns from any AI assistant.Local · stdionpm: adrex-ai
AdrMcpMCP server for Architectural Decision Records: navigate, author, validate, link, and analyze them.Local · stdioNuGet: AdrMcp
AdsBuy Telegram subscribers and website traffic, billed per verified result.Remote · HTTPLive check: sign-in requiredmcp.promtpress.com
Ads MCPMCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.Local · stdionpm: @gudlab/ads-mcp
AdsAgent - Google Ads MCPHosted Google Ads MCP with OAuth, bounded reads, and prepare/confirm writes.Remote · HTTPLive check: sign-in requiredgoogle.adsagent.md
AdsAgent - Meta Ads MCPHosted Meta ads MCP with OAuth, bounded reads, and prepare/confirm writes.Remote · HTTPLive check: sign-in requiredadsagent.md
AdsapLaunch and manage Meta and Google Ads from your AI assistant. You approve every change first.Remote · HTTPLive check: sign-in requiredmcp.adsap.ai
AdscapiFire one canonical conversion event to every ad platform's server-side Conversions API.Local · stdionpm: adscapi