google-ads-mcp-coolify

Perfect for teams running self-hosted MCP infrastructure on platforms likeCoolify,Dokploy,EasyPanel,Railway,Render,Fly.io, or any plain Docker/Kubernetes setup.

- Privacy: your Google Ads OAuth tokens never leave your infrastructure.
- Multi-client: one deployed instance serves Claude Code, Cursor, Continue, Zed, n8n, and any other MCP-compatible tool.
- No paid SaaS gateway: skip third-party MCP relays — go straight from your AI client to your VPS to the Google Ads API.
- Works behind reverse proxies: HTTPS via Let's Encrypt, custom subdomain, optional auth middleware.

- ✅Streamable HTTP transport(MCP spec) — works with all modern MCP clients
- ✅OAuth 2.0with auto refresh — no manual token rotation
- ✅Bearer token authbuilt-in (MCP_AUTH_TOKEN) — endpoint never publicly accessible by default
- ✅Env-var credentials(GOOGLE_ADS_CREDENTIALS_JSON) — no File Mount required on Coolify
- ✅Single subdomain deploy—https://google-ads-mcp.yourdomain.com/mcp
- ✅Multi-account / MCC supportviaGOOGLE_ADS_LOGIN_CUSTOMER_ID
- ✅Built on FastMCP— fast, async, production-grade
- ✅Up-to-date upstream: each build pulls the latestgomarble-ai/google-ads-mcp-serverfrommain
- ✅Coolify-tested— also runs on Dokploy, EasyPanel, Railway, Fly.io, plain Docker

┌─────────────────┐ HTTPS ┌────────────────────────┐ OAuth ┌──────────────────┐ │ Claude Code / │ ──── /mcp ─────────▶│ This container │ ──── refresh ────▶ │ Google Ads API │ │ Cursor / etc. │ │ (FastMCP HTTP server) │ │ (v19) │ └─────────────────┘ └────────────────────────┘ └──────────────────┘ │ ▼ /app/credentials/credentials.json (mounted as a file by Coolify)

The container does three things at startup:
- Loads OAuth tokens from/app/credentials/credentials.json(file mount).
- Imports the FastMCP app defined in the upstreamserver.py.
- Runs it on0.0.0.0:8000usingstreamable-httptransport.

Coolify → + New Resource → Public Repository

GAQL reference is exposed as an MCP resource:gaql://reference.

This wrapper ships withbuilt-in Bearer token auth(MCP_AUTH_TOKENenv var). Set it and the endpoint requiresAuthorization: Bearer <token>on every request — no token, no access.

python3 -c 'import secrets; print(secrets.token_urlsafe(32))' # or: openssl rand -base64 32

For team deployments, additional hardening worth considering:

- Per-user tokens with revocation— back the middleware with a Supabase/Postgres table of token hashes (planned in a future release; PRs welcome)
- Cloudflare Access / Tailscale / WireGuard— zero-trust SSO in front of the endpoint
- IP allowlistat the Coolify/Cloudflare layer if connecting from a fixed set of machines

Even withMCP_AUTH_TOKEN, treat the endpoint as a defense-in-depth boundary, not the only line of defense — rotate the token periodically.

sh: tsc: not foundor build fails with missing devDependencies

You're hitting the Coolify env-var-as-build-ARG quirk.Don't setNODE_ENV=productionas an env var on the Coolify service.That gets injected as a build ARG and breaks unrelated Dockerfiles. (This repo is Python, but the same pattern bites Node-based MCP servers.)

CheckBase Directory =/andDockerfile Location =/Dockerfilein the Coolify Configuration tab.

401 Unauthorized/OAuth credentials expired

Opencredentials.jsonand confirmrefresh_tokenis present. If it's missing, regenerate viagen_credentials.pyand re-upload the file mount.

You're querying through a Manager (MCC) account. SetGOOGLE_ADS_LOGIN_CUSTOMER_ID=<mcc_id_without_dashes>and redeploy.

Container started but isn't listening on port 8000. Check the build logs — most often thegit cloneof upstream failed. Re-trigger the deploy.

- Optional auth middleware (Bearer / Basic / IP allowlist)
- Pinned upstream SHA option (currently builds againstmain)
- Helm chart / Kubernetes manifests
- Examples for n8n, Make, Zapier MCP integrations

Keywords: google ads mcp server, google ads mcp coolify, self-hosted mcp google ads, mcp server docker, deploy mcp server vps, claude code google ads integration, fastmcp http server, google ads api claude, mcp streamable http, model context protocol google ads, cursor google ads mcp, n8n google ads mcp, self host model context protocol, google ads oauth mcp.

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Google Ads reporting and campaign management for Claude; everything it creates starts paused, nothing spends until you turn it on.

Connect your Google Ads and Meta accounts to Claude, Cursor, or any AI tool that supports MCP.

Connect Google Ads to Claude or ChatGPT via Two Minute Reports MCP and get accurate answers about campaigns, creatives, and spend.

Supervised Meta Ads operating system for Claude Code - 57 tools for campaign management, multi-asset ads, targeting, pixel diagnostics, catalogs, and safety gates

Mercopilot connects your Shopify store and your Google Ads account to Claude, ChatGPT, and other AI assistants through a standard called MCP. Once connected, you ask your AI assistant plain-English questions about your store and your ad spend, get a ranked list of what to fix and where to grow, and approve specific changes that are made directly in Shopify or Google Ads. No separate dashboard to monitor, no reports to download.

A shared campaign canvas for you and your AI agent: briefed by your brand rules, gated by your approval.

Run your Linkedin account from claude or chatgpt

Chat with any brand's Meta (Facebook/Instagram) ads inside Claude — research a competitor's ad library, surface their longest-running winners, extract hooks/formats, and clone winning ads for your own brand.

Self-hostable AGPL SEO manager backend with an MCP server for keyword research, content queue, and SERP tracking, built for Claude Code.