mcpbeat Sign in

AdAce Ads MCP Server

answering

AdAce Ads is answering right now. Last checked 12 min ago.

Google Ads and Meta Ads from Claude or ChatGPT: live reports, wasted spend, changes you approve.

Uptime history 48 hours of history
48 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
137 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check AdAce Ads every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add ads --transport http https://ads.adace.website/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ads": {
      "url": "https://ads.adace.website/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ads]
url = "https://ads.adace.website/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ads": {
      "url": "https://ads.adace.website/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ads": {
      "url": "https://ads.adace.website/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://ads.adace.website/mcp streamable-http sign-in 132 ms 12 min ago

Alternatives to AdAce Ads

same job, measured the same way
LoomaScale Ads
by loomascale

Run Google Ads and Meta Ads from ChatGPT or Claude: audit wasted spend, create and manage campaigns.

answering
adplane
by adplane

Google, Meta, Microsoft and TikTok Ads in Claude or ChatGPT: reports and changes, created paused.

answering
Admiral
by meetadmiral

Ask Claude or ChatGPT about your own Google Ads and Meta ad accounts.

answering
Adsap
by adsap

Launch and manage Meta and Google Ads from your AI assistant. You approve every change first.

answering
Adako: ad ops for AI assistants
by adako

Google, Meta, LinkedIn and ChatGPT Ads for AI assistants. Every change needs your approval.

answering
Com
by com-adseditor

Ads Editor MCP: 212 tools to run Meta Ads and Google Ads from Claude, ChatGPT, Codex and Cursor.

answering
Opus Growth, Ad Platforms MCP Connector
by opusgrowth

Run Google, Meta, Microsoft, TikTok and LinkedIn Ads from Claude or ChatGPT. Writes need approval.

answering
Agency AI – Meta & Google Ads Automation
by agencyai

Create, launch, and manage Meta + Google ads from Claude and ChatGPT.

answering

AdAce Ads — questions

Answers built from our own checks of this server.

Why is there no tool list for AdAce Ads?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is AdAce Ads working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 137 ms. The bar chart above shows every period we have measured.
How do I connect AdAce Ads?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to AdAce Ads?
No API key is involved. AdAce Ads answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is AdAce Ads?
It answers our handshake in 137 ms on average, which is faster than 74% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.