DEXUN AdWhiz MCP Server

Let Claude Desktop / Cursor / any MCP-aware client talk to your DEXUN AdWhiz account. Ask Claude things like:

"List my connected ad accounts." "What's the AI recommending I do right now?" "Have there been any sign-ins from new IPs this week?" "How close am I to my API rate limit?"

Read-only for now (v0.1) — Claude can see your AdWhiz state but can't apply changes or pause campaigns. Mutation tools land in a later version once the optimizer exits shadow mode.

What you need

• Node.js 18 or newer (node --version)

• A DEXUN AdWhiz account (sign up free)

• A DEXUN AdWhiz API key — generate one at /settings#api-keys

• Either:

  • Claude Desktop (recommended)

  • Cursor with MCP enabled

  • Any other MCP-aware client

No npm install required. The server is a single Node script with zero runtime dependencies.

Related MCP server: flin-meta-ads-mcp

Install

Claude Desktop

1. Clone or download this repo somewhere stable on your machine:

   git clone https://github.com/dexun-inc/adwhiz-mcp.git ~/.adwhiz-mcp

2. Open Claude Desktop's MCP config file. On macOS:

   ~/Library/Application Support/Claude/claude_desktop_config.json

   On Windows:

   %APPDATA%\Claude\claude_desktop_config.json

3. Add the adwhiz entry to mcpServers:

   {
     "mcpServers": {
       "adwhiz": {
         "command": "node",
         "args": ["/absolute/path/to/.adwhiz-mcp/src/index.mjs"],
         "env": {
           "ADWHIZ_API_KEY": "dxk_live_PUT_YOUR_KEY_HERE"
         }
       }
     }
   }

   Replace the path with where you cloned the repo, and the API key with one from /settings#api-keys.

4. Quit Claude Desktop completely and reopen. The 5 AdWhiz tools should now show up when you start a new conversation.

Cursor

1. Same git clone step.

2. Open Cursor → Settings → Features → Model Context Protocol → Add server.

3. Use the same command + args + env shape as Claude Desktop.

Other MCP clients

Any client that follows the MCP spec can use this. The server speaks plain JSON-RPC 2.0 over stdio. Tell the client to run node /path/to/src/index.mjs and set ADWHIZ_API_KEY in the spawn environment.

What Claude can do

All five are read-only. They never apply budget changes, pause campaigns, or revoke keys. To do those things use the dashboard.

Environment

Troubleshooting

Claude says "Server adwhiz is not responding" or the tools don't appear. Run the script manually to see stderr output:

ADWHIZ_API_KEY=dxk_live_... node /path/to/src/index.mjs

It should sit idle waiting for stdin. If it errors immediately, the message tells you what's wrong (most commonly: API key missing or node is too old).

Tools error with "Unauthorized". Your API key was revoked or you copied it wrong. Generate a fresh one at https://app.7275.com/settings#api-keys.

Rate limited. You're hitting your plan's per-key RPM cap (60/120/600/3000 RPM by tier). Either wait for the window to reset (get_quota tells you when) or upgrade.

Security model

• The MCP server runs locally on YOUR machine. Your API key never leaves your machine.

• All HTTP requests go directly to app.7275.com over HTTPS.

• Claude sees only the data the tools return — same data your dashboard shows you.

• This server is open source. Audit it before installing on a sensitive machine.

Versioning

• v0.1 — Read-only tools: list accounts / recommendations / activity / quota / identity.

• v0.2 (planned) — apply_recommendation once auto-apply is calibration-gated.

• v0.3 (planned) — pause_campaign + change_budget direct mutations.

License

MIT — see LICENSE.

Issues / questions

Bug reports + feature requests: open an issue on the main repo or email service@7275.com.

Privacy Policy

This extension talks only to the DEXUN AdWhiz API (https://app.7275.com/api/v1) using the API key you configure. It reads your ad-account metadata, AI recommendations, savings summary, and audit events — it never modifies campaigns or spends money, and it sends no data to any third party.

Full policy: https://www.7275.com/en/legal/privacy