adwhiz

---
name: adwhiz
description: >
  Manage Google Ads & Meta (Facebook) Ads from your AI coding tool. 102 MCP
  tools for auditing, creating, and optimizing ad accounts using natural language.
metadata:
  openclaw:
    primaryEnv: "ADWHIZ_API_KEY"
    requires:
      env:
        - "ADWHIZ_API_KEY"
    homepage: "https://adwhiz.ai"
    source: "https://github.com/iamzifei/adwhiz"
    license: "MIT"
---

# AdWhiz — Google Ads & Meta Ads MCP Server

AdWhiz is a hosted MCP server that connects your AI coding tool to the
Google Ads API and Meta (Facebook) Graph API through a secure, authenticated
proxy. It exposes **102 tools** across 7 categories so you can audit, create,
and manage ad campaigns across both platforms using plain English.

All API calls are authenticated via your personal `ADWHIZ_API_KEY` and routed
through the AdWhiz server at `mcp.adwhiz.ai`. No Google or Meta credentials
are stored by the skill — authentication is handled entirely server-side
after you link your ad accounts at https://adwhiz.ai/connect.

## Security & Permissions Model

- **OAuth 2.0**: User authenticates with Google and/or Meta via AdWhiz's web
  UI. Refresh tokens (Google) and long-lived access tokens (Meta) are encrypted
  at rest (AES-256-GCM) and never exposed to the agent.
- **API key scoping**: Each `ADWHIZ_API_KEY` is bound to a single user's
  connected accounts. Cross-user access is not possible.
- **Write safety**: All Google Ads write tools create entities in **PAUSED**
  status by default. Meta write tools require explicit status parameters.
- **Mutation logging**: Every mutation is recorded in the `get_operation_log`
  tool for full auditability.
- **Read-only by default**: 39 of 102 tools are strictly read-only and cannot
  modify your accounts.
- **Confirmation required**: Write tools require user confirmation before
  executing via the agent's standard permission flow.
- **No arbitrary code execution**: The MCP server is a hosted HTTP service.
  No code is downloaded o