Fudge MCP vs Google Ads MCP Server: Features, Pricing & Which Is Better (2026)
A side-by-side comparison of Fudge MCP and Google Ads MCP Server — features, pricing, and ideal use cases — to help you decide which AI tool fits your workflow.
Fudge MCP
Fontofweb
MCP server that lets AI coding agents search real websites for fonts, color palettes, and UI patterns instead of inventing them.
Key features
- Design Reference Search: Query nearly 10,000 real websites by font, color palette, component, layout, or visual similarity.
- MCP Server for Agents: Connects to any MCP-compatible client (Claude Code, Cursor, Windsurf) so agents can pull design evidence during code generation.
- Real Design Tokens: Returns measured fonts, hex codes, and spacing pulled from live sites so agents stop hallucinating design values.
- Chrome Extension Capture: Save new references from any site you visit; captured pins become searchable by agents you use.
- Screenshot Evidence: Every match is grounded in a real screenshot so agents and designers can visually verify inspiration.
- Design Token Export: Export a chosen theme's tokens for use in code or a design system.
- Local-First MCP: Runs locally so your saved reference library and agent traffic stay on your machine.
Best for
- Vibe-Coded App Styling: Give an AI-built prototype the visual polish of a real production site instead of a stock template.
- Design System Discovery: Explore how similar SaaS products handle typography and color before finalizing a design system.
- Font Pairing Research: Find real websites using a target typeface and see what secondary fonts pair well.
- Palette Sourcing: Search by color to find production sites with a compatible palette and copy the exact hex values.
- Agent-Assisted UI Iteration: Have Claude Code or Cursor pull three inspiration references before editing a component.
- Design Reviews: Curate a captured board of competing product pages to inform a redesign decision.
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.