MCP Ads

MCP Ads: Google Ads MCP server + Meta Ads MCP server

MCP Ads, the ads MCP server by Roy Azran. Hosted at mcp-ads.com, open source here.

Website · Docs · Pricing · MCP Registry listing (com.mcp-ads/mcp-ads)

Open-source (MIT) MCP server for Google Ads, Meta Ads (Facebook & Instagram), GA4, Search Console, Tag Manager, TikTok, LinkedIn, Microsoft Ads and more. Works with Claude, Claude Code, ChatGPT, Cursor, Codex, Gemini CLI, Grok, or any MCP client. Read performance, audit wasted spend, build reports, and create or change campaigns. Everything it creates starts paused until you say otherwise.

3,363 registered actions across 21 tool families in the hosted build (September 2026), exposed through one dispatcher per family so your agent loads about two dozen tool definitions instead of thousands. This repo ships 18 of those families; see Tool categories.

How it compares

Facts as of September 2026, taken from each product's public pages. Plans and coverage change, so check their site before deciding.

Use Google's or Meta's server if you only need one platform and want the vendor's own code. Use this one if you want one server across platforms, write access to Google Ads, or the option to run the whole thing yourself.

---

Choose your path

☁️ Cloud — connected in 2 minutes

Go to [mcp-ads.com](https://mcp-ads.com?utm_source=github&utm_medium=readme&utm_campaign=oss_repo), sign in, OAuth your ad accounts in the browser, and paste one URL into Claude. Done.

• No API applications, no developer tokens, no app reviews — the platform approvals (Google Ads developer token, Meta App Review, and the rest) are already in place
• $49/month flat for every platform, with a 7-day free trial (see pricing for the current offer)
• Your credentials stored encrypted; revoke any time from the dashboard

This is the right choice for almost everyone who wants to *use* the tools rather than *host* them.

🔧 Self-hosted — free forever, your keys, your machine

Clone this repo and run it with your own platform credentials. MIT licensed, no strings, no phone-home. Your tokens never leave your machine.

The honest cost: several of the ad platforms make you apply for API access (see the table below). If you already have those credentials — you're an agency with a Google Ads developer token, a developer with a reviewed Meta app — self-hosting takes minutes. If you don't, budget days to weeks for the platforms' own approval queues, or just use the cloud.

Same code either way. The hosted product is this server plus multi-user auth, the approvals already done, and three families not in this repo yet (Merchant Center, X Ads, Bing Webmaster Tools).

---

Connect to your AI client

The hosted endpoint is the same for every client:

https://mcp-ads.com/mcp-slim

Sign-in is OAuth in the browser on first use; there is no API key to paste. For a self-hosted server, use the stdio config under Self-hosted quick start instead; the note under each client says where it goes.

Claude.ai and Claude Desktop. Settings → Connectors → Add custom connector, paste the URL above, then approve the sign-in window. (Guide) Self-hosted: Claude Desktop takes the command/args block in claude_desktop_config.json.

Claude Code.

claude mcp add --transport http mcp-ads https://mcp-ads.com/mcp-slim

The first tool call opens the browser sign-in. (Guide) Self-hosted: claude mcp add mcp-ads -- python /absolute/path/to/mcp-ads/server.py, or the same block in .mcp.json.

ChatGPT. Custom connectors need Developer mode:

1. Settings → Plugins → Browse plugins, and turn Developer mode on (one time).
2. Settings → Connectors → Add custom connector. Name it "MCP Ads" and paste the URL above.
3. Sign in with the Google identity that has access to your ad accounts.
4. In a new chat, open the tools menu and switch the connector on. ChatGPT keeps connectors off per chat by default.

(Guide with a recording)

Cursor. Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project) and restart Cursor:

{

"mcpServers": { "mcp-ads": { "url": "https://mcp-ads.com/mcp-slim" } } }

(Guide) Self-hosted: the same file takes the command/args block instead of url.

Codex. Add [mcp_servers.mcp-ads] with url = "https://mcp-ads.com/mcp-slim" to ~/.codex/config.toml. (Guide)

Gemini CLI. Add an mcp-ads entry with the URL to ~/.gemini/settings.json and run /mcp to check it. (Guide)

Grok. On grok.com: + → Connectors → New Connector → Custom, paste the URL and finish the sign-in. (Guide)

---

Self-hosted quick start

git clone https://github.com/RoyAzran/mcp-ads.git

cd mcp-ads pip install -r requirements.txt cp .env.example .env # fill in the platforms you use python server.py doctor # shows what's connected

Then add it to Claude Desktop (claude_desktop_config.json) or Claude Code (.mcp.json):

{

"mcpServers": { "mcp-ads": { "command": "python", "args": ["/absolute/path/to/mcp-ads/server.py"] } } }

That's the whole install. Ask your agent *"audit my Google Ads wasted spend"* and watch it go.

Docker instead:

cp .env.example .env

docker compose up -d # HTTP server on 127.0.0.1:8000, MCP endpoint at /mcp

HTTP mode without Docker: python server.py serve --transport http

OAuth helper for the bearer-token platforms (opens a browser, stores and auto-refreshes the token):

python server.py auth snapchat_ads

What works out of the box, honestly

Self-hosting means holding your own keys to each platform. Some hand them over in minutes; some make you apply. This is the real picture:

If that table makes you tired, that's exactly what [the cloud version](https://mcp-ads.com?utm_source=github&utm_medium=readme&utm_campaign=oss_repo) is for — the approvals are done, you just connect your accounts.

Tool categories

One dispatcher per family. Counts are registered actions in the hosted build (September 2026); each dispatcher links to its API reference page.

| microsoft_ads_action | 11 | microsoft_ads_campaign_performance, microsoft_ads_list_keywords, `microso