Otto

What is Otto?

Otto provides a remote Google Ads MCP server that lets you launch and manage Google Ads from within an MCP client (for example, Claude). Instead of running an MCP server locally or doing terminal/JSON setup, you connect to Otto by pasting a single MCP URL into your client and then authenticate with Google.

The core purpose is to act as a hosted bridge between your MCP client/agent workflows and Google Ads actions such as building campaigns, applying best-practice checks, and generating reporting outputs.

Key Features

• Hosted remote MCP server connection via a paste-in URL, so you can start from your MCP client without local server setup
• OAuth-based access aligned to the MCP auth spec, with scoped tokens for the Otto server rather than exposing local files
• Campaign editing controls for Search: create campaigns and ad groups, add keywords, and draft RSA ads
• Built-in hygiene and review workflow: auto-tagging checks, auto-application of reviews, and disapproval snapshots
• Reporting and export support across campaign structure and performance fields (including campaign/ad group/ads/keywords, devices, geo, and search terms) plus CSV export via a signed download link
• Keyword Planner capability that generates keyword ideas from seed phrases or a URL and pulls historical metrics for known keywords
• Geo + language targeting and per-location results, plus the ability to create/attach lists and review search terms for safety

How to Use Otto

1. Connect the MCP server in your client (example given for Claude): open Claude settings → Connectors → Add Custom Connector → paste the Otto MCP URL: https://googleads.hireotto.com/mcp.
2. Complete the connection handshake: a Google sign-in window opens for Otto to recognize your workspace; approve the prompt.
3. Authenticate Google Ads: in Claude, run prompts such as “Connect Google Ads” or “Authenticate Google Ads.” Claude returns an auth link—open it and grant access.
4. Select the Google Ads accounts Otto can access when prompted, then close the auth window and return to Claude.
5. Verify access with a simple prompt such as “List my accessible accounts” or “List campaigns for 123‑456‑7890.”

Use Cases

• PPC management with an agent: Use an MCP-capable AI client to create or update Search campaigns and ad groups, add keywords, and draft RSA ads without leaving the chat/workflow.
• Ongoing ad/account hygiene: Request auto-tagging checks and review/disapproval snapshots to keep campaign changes aligned with established “clean hygiene” practices and to reduce common papercuts.
• Search-term safety and negative keyword workflow: Review search terms, create or attach lists, and keep waste out by generating negative or safety-related updates as part of your agent-driven process.
• Keyword research with programmatic outputs: Generate keyword ideas from seed phrases or a URL using Keyword Planner features, then pull historical metrics for known keywords and export results via CSV for further analysis.
• Reporting from structured context: Ask for reporting across campaigns/ad groups/ads/keywords and dimensions like devices, geo, and available conversion-related fields, then download a signed CSV link for programmatic review.

FAQ

Which clients are supported?

The page describes using MCP clients such as Claude. Compatibility beyond MCP clients is not specified.

Do I need Google Cloud or terminal steps?

No. The page states there’s no Google Cloud setup, no JSON edits, and no terminal steps; you connect by pasting the MCP URL into your MCP client.

Will this change my campaigns automatically?

The page indicates you can use the server to build and edit campaigns (create campaigns/ad groups, add keywords, draft RSAs) and apply hygiene/review workflows, but it does not specify whether changes apply automatically without approval in your workflow.

What happens during authentication?

You’ll complete a Google sign-in handshake, then run an authentication prompt in Claude that returns a link. You grant access and select which Google Ads accounts Otto can access.

How can I contact support?

The provided content shows a “How do I contact support?” FAQ item, but it does not include support details or a contact method.

Alternatives

• Run a local MCP server for Google Ads: If you already operate MCP servers locally, you may prefer hosting and configuring your own Google Ads integration, but that typically involves local setup rather than a paste-in remote URL.
• Use a Google Ads automation or scripting approach: Alternatives include using Google Ads scripts or other automation tools that perform campaign operations, but they may not integrate as directly into MCP/agent workflows.
• Use a reporting-first tool (CSV-based): If your main need is exports and reporting rather than in-chat editing, you can use tools that produce CSV reports for campaigns, keywords, search terms, and geo/device breakdowns, then handle analysis outside the MCP workflow.
• Use an MCP tool focused on other ad platforms: For teams that need multi-platform ad management, you can look for MCP servers or integrations that focus on a specific platform workflow and then standardize your agent prompts across providers.