Google Ads MCP Server vs Kit for AI: Features, Pricing & Which Is Better (2026)
A side-by-side comparison of Google Ads MCP Server and Kit for AI — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.
Google Ads MCP Server
HireOtto
Hosted and open-source Model Context Protocol server to manage Google Ads from MCP clients (e.g., Claude) without Google Cloud or terminal setup.
Key features
- Hosted Remote MCP Server: A hosted endpoint that lets MCP clients (for example Claude Desktop) call Google Ads management tools without requiring Google Cloud setup, terminal use, or manual JSON edits.
- Self-Hosted Node.js/TypeScript Implementation: Open-source repositories provide Node.js and TypeScript servers you can run locally or in containers with simple .env-based configuration for Google Ads API credentials.
- Campaign Management Tools: Programmatic creation, retrieval, update, and budget adjustments for campaigns and ad groups, including parameters like campaign_id and budget_euros for direct modification.
- Unified MCP Tooling Endpoint: All tools are exposed via a consistent POST /api/mcp interface and support MCP streamable HTTP JSON-RPC (initialize, tools/list, tools/call) for agent interoperability.
- Analytics & Reporting: Export campaign and performance reports to CSV or JSON, request date-range filtered metrics, and retrieve conversion and cost statistics for optimization and reporting.
- Rate-Limit Handling & Retries: Built-in handling of Google Ads API rate limits with automatic retries to reduce manual error-handling and throttle issues.
- OAuth2 & Simple Configuration: Supports standard Google Ads OAuth2 credentials (client id/secret, refresh token, developer token) with inline JSON in .env for straightforward setup.
- Extensible Tools & Workflows: Modular tool implementations (accounts, campaigns, ads, keywords, conversions, performance, shopping) allowing customization and addition of new MCP tools.
- MCP-compatible toolset exposing Google Ads operations (campaigns, ad groups, ads, keywords, conversions, performance, analytics, shopping).
- POST /api/mcp endpoint with ToolResponse shape ({ok:true,data} | {ok:false,error}) and support for MCP Streamable HTTP JSON-RPC (initialize, tools/list, tools/call).
- Campaign management operations (create/update budgets, retrieve campaign stats).
- Analytics & reporting with export options to CSV or JSON (export_report with parameters: format, days).
- Autocomplete/keyword-sourcing tools (Google Autocomplete, Trends, keyword clustering in some forks).
- Configuration via .env (inline JSON or environment variables) and example .env templates included.
- OAuth2 support: instructions and scripts to obtain refresh tokens; requires Google Ads developer token, client ID/secret, refresh token, optional login-customer-id.
- Automatic handling of Google Ads API rate limits and retry logic.
- Multiple installation options: npm/pnpm (local/global), npx (no install), Docker images available on GHCR.
- Claude Desktop integration helpers and example claude_desktop_config.json for adding to MCP clients.
Best for
- Agent-driven Campaign Launches: Use an MCP-capable agent (like Claude) to create and configure Google Ads campaigns via natural-language prompts without touching Google Cloud or API JSON.
- Daily Campaign Monitoring and Alerts: Query campaign performance and get daily summaries or alerts from the MCP server for rapid status checks and anomaly detection.
- Automated Budget Optimization: Programmatically adjust daily budgets and bids across accounts using scheduled agent workflows or triggered rules exposed through MCP tools.
- Exporting Stakeholder Reports: Generate CSV or JSON exports of campaign, conversion, and cost metrics for sharing with teams or importing into BI tools.
- Keyword & Trend Research Integration: Combine Google Autocomplete, Trends, and Search Console-derived keyword data (available in some implementations) to inform campaign targeting from the same MCP endpoint.
- Local Development and Custom Extensions: Developers can run the open-source server locally, add custom tools (e.g., custom analytics or bidding strategies), and integrate with CI/CD or containerized deployments.
- Integrating Ads Management into ChatOps: Embed Google Ads operations into chat-based workflows or agent orchestrations so non-technical marketers can request changes conversationally.
- Manage Google Ads campaigns programmatically from an MCP-enabled chat assistant or desktop client (e.g., create/update campaigns, budgets).
- Run daily campaign monitoring and automated campaign optimization workflows via LLM agents.
- Export campaign reports for analysis (CSV/JSON) and feed results back into an agent for decision-making.
- Perform keyword research and clustering by combining Google Autocomplete/Trends data with Search Console (in supported forks).
- Integrate Google Ads controls into internal tooling without exposing direct Google Cloud or manual JSON configuration to non-technical users.
Kit for AI
Kit for AI
MCP-native memory + knowledge platform: turn any file, URL, or YouTube video into grounded, searchable context for any LLM agent.
Key features
- MCP Memory Tools: remember, recall, and search exposed as native MCP tools any agent can call mid-conversation to persist users, preferences, and decisions.
- Document Conversion: Converts PDF, Word, Excel, PowerPoint, CSV, HTML, and images (OCR) to clean Markdown ready for LLM ingestion.
- URL → Markdown: Extracts main content from JS-heavy, gated, and region-specific web pages into clean Markdown with tables preserved.
- YouTube Transcripts as Docs: Paste a YouTube link and the transcript becomes a searchable, citable document in a knowledge base.
- Hybrid Semantic Search: Combines vector embeddings with full-text search, fused via RRF and reranked for precise cited retrieval.
- Knowledge Bases with Citations: Group documents into KBs with grounded chat, cited answers, feedback corrections, and a visual doc graph.
- Token-efficient Retrieval: Pulls only the passages an agent needs, cutting token usage by up to 90% versus dumping whole documents.
- Private by Default: Files encrypted at rest, API keys hashed, spaces isolate projects, and data is never used for training.
Best for
- Give any MCP agent persistent memory: Attach Kit to Claude, Cursor, or a custom agent and let it remember users, preferences, and decisions across sessions.
- RAG pipelines without the stack: Ingest company docs, chunk and embed automatically, and query via one API instead of stitching a vector DB and reranker.
- AI support bots with citations: Ground a support agent on product docs so answers cite the exact passage they came from.
- Chat with YouTube content: Turn lectures, talks, and tutorials into searchable knowledge for research or content workflows.
- Invoice and form extraction: Use JSON extraction to pull typed fields from documents into a user-defined schema.
- Clean scraping replacement: Convert URLs to Markdown for training data, fine-tuning datasets, or agent context.