THE Google Ads MCP Server
Turn your MCP client into a Google Ads agent.
Paste one URL. That's it! No Google cloud, json setup.
Built by a marketer, for marketers.
Copy this URL to get started:
☁️ Fully hosted
Most MCP servers run locally and expect terminal work.
Otto is remote: paste the URL in your client and go.
🔒 Safer by design
OAuth-based access aligned with the MCP auth spec.
Tokens are scoped to this server, no local files exposed.
🎯 Built for real PPC
Opinionated defaults based on established best practices
Fast setup, clean hygiene, fewer papercuts.
Build & Edit (Search)
Create campaigns/ad groups Add keywords, draft RSAs Budgets, networks, toggles
Hygiene & Reviews
Auto-tagging checks Auto-apply review Disapprovals snapshot
Reporting
Campaigns, ad groups, ads, keywords Devices, geo, search terms Conv./IS where available
Negatives & Safety
Create/attach lists Review search terms Keep waste out
Keyword Planner
Keyword ideas from seed phrases or URL Pull historical metrics for known keywords Geo + language targeting and per-location results
CSV exports
Clean inline summary + signed CSV download link MCP client/agent can analyze the file programmatically without burning context
Installation steps
Step 1
Add the server
Claude → Settings → Connectors → Add Custom Connector → paste: https://googleads.hireotto.com/mcp
Step 2
Connect
A Google sign‑in window opens. This is a quick handshake so Otto can recognize your workspace. Approve the prompt.
Step 3
Successfully connected
You’ll see “Successfully connected” in Claude (blue banner). That confirms Otto is reachable as a remote MCP server.
Step 4
Authenticate Google Ads
Try a plain-English prompt like “Connect Google Ads” or “Authenticate Google Ads.”
Claude will return a link - open it and grant access. During this step you’ll also be asked to select which Google Ads accounts Otto can access.
When the auth page says you’re done, close that window and return to Claude. Otto is now fully set up.
Step 5
Sanity check
Ask for something simple like “List my accessible accounts” or “List campaigns for 123‑456‑7890.”
My Story
Why I'm building Otto😼
Suyash Chaudhari
Otto’s Human-in-the-Loop
2019 - 2020
DV360 Ops
GroupM Bootcamp
First taste of high‑stakes toggles; built my own tracking sheets to avoid budget‑meltdowns. Efficiency bug officially implanted.
2021
Account Manager
MightyHive Playbook
Saw how seasoned teams script the boring bits—Sheets add‑ons pulling DV360 data, pivots building themselves. Aha: automation beats copy‑paste.
2021 - 2022
First-Time Founder
Co‑founded SalesJarvis
Tried to automate SDR workflows; learned the hard truth that headcount ≠ expertise. Fell in love with process automation anyway.
2023 - 2024
First‑Marketer Grind
Solo growth lead at a SaaS startup
Generated $300 k pipeline, 53 % of net new revenue, and at least three new grey hairs while manually babysitting Google Ads. Conclusion: caffeine scales; human focus doesn’t.
May 2025
Waitlist open
Otto pounces into the wild
I decide my cat‑nap schedule can survive one more SaaS product, so I push Otto out of the cardboard box and onto the Internet.
