com.7275/adwhiz
Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.
Open source Open in the app JSON README (API)
About
Read-only MCP access to your DEXUN AdWhiz account: ad accounts, AI recommendations, savings.
Details
- Kind
- MCP servers
- Topic
- Marketing & analytics
- Publisher
- com.7275
- Origin
- official
- Category
- ferramentas
- Transport
- http
- Version
- 0.2.0
- Added
- 2026-08-29 03:00:51
- Updated
- 2026-08-29 03:00:51
- Origin id
com.7275/adwhiz
README
# DEXUN AdWhiz MCP Server
Let Claude Desktop / Cursor / any [MCP](https://modelcontextprotocol.io)-aware client talk to your [DEXUN AdWhiz](https://app.7275.com) 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](https://app.7275.com))
- A DEXUN AdWhiz API key — generate one at [/settings#api-keys](https://app.7275.com/settings)
- Either:
- [Claude Desktop](https://claude.ai/download) (recommended)
- [Cursor](https://cursor.sh) with MCP enabled
- Any other MCP-aware client
No `npm install` required. The server is a single Node script with zero runtime dependencies.
## Install
### Claude Desktop
1. Clone or download this repo somewhere stable on your machine:
```bash
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`:
```json
{
"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](https://app.7275.com/settings).
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
| Tool | Use when the user asks |
| --------------------- | --------------------------------------------------------------------- |
| `list_ad_accounts` | "What accounts do I have connected?" / "Show me my Meta accounts" |
| `list_recommendations`| "What does the AI recommend right now?" / "Anything to do today?" |
| `get_savings_summary` | "How much has AdWhiz saved me?" / "Is the AI actually working?" |
| `get_recent_activity` | "What happened this week?" / "Any sign-ins I didn't make?" |
| `get_quota` | "Am I close to my rate limit?" / "How much API quota do I have?" |
All five are read-only. They never apply budget changes, pause campaigns, or revoke keys. To do those things use [the dashboard](https://app.7275.com/dashboard).
## Environment
| Variable | Default | Notes |
| ----------------- | ---------------------- | ------------------------------------------------------------------ |
| `ADWHIZ_API_KEY` | _(required)_ | `dxk_live_*` or `dxk_test_*`. Generate at /settings#api-keys. |
| `ADWHIZ_BASE_URL` | `https://app.7275.com` | Override for self-hosted / staging environments. |
## Troubleshooting
**Claude says "Server adwhiz is not responding" or the tools don't appear.**
Run the script manually to see stderr output:
```bash
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](./LICENSE).
## Issues / questions
Bug reports + feature requests: open an issue on the main repo or email service@7275.com.