AdButler vs Affset
A side-by-side look at the AdButler and Affset MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AdButler for marketing work as a local process; choose Affset for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AdButler when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ADBUTLER_API_KEY. - You want tools like
list_advertisers, get_advertiser, create_advertiser.
Choose Affset when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You want tools like
whoami, get_stats, list_campaigns.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ADBUTLER_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 627 | 31 |
| Full listing | View AdButler | View Affset |
Tools & capabilities
AdButler tools 627
list_advertisersList all advertisers in your AdButler accountget_advertiserGet details of a specific advertiser by IDcreate_advertiserCreate a new advertiserupdate_advertiserUpdate an existing advertiserdelete_advertiserDelete an advertiserarchive_advertiserArchive an advertiser (soft-delete, can be restored later)list_archived_advertisersList all archived advertisersget_archived_advertiserGet details of a specific archived advertiserunarchive_advertiserRestore an archived advertiser back to active statuslist_all_campaignsList all campaigns across all typeslist_campaignsList all standard campaignsget_campaignGet details of a specific standard campaign- +615 more on the listing page
Affset tools 31
whoamiShow the tenant this server is bound to: namespace, API base, derived dashboard URL, and (when readable) company / timezone / custom API domain. Read-only.get_statsTraffic stats grouped by a dimension (date, campaign, zone, country, sub1–5, advertiser, publisher, …), optionally narrowed with `advertiser_email`/`publisher_email` filters (one user, any group_by). Returns clicks, conversions, CR, payout, media cost and ROI as a table. `paid_only` defaults to tru…list_campaignsList campaigns (status / name filter, pagination).get_campaignOne campaign's full record — every field (untruncated offer URL, exact schedule, budgets/pacing, silent flag, payout goal type) plus its targeting rules and payout rules, in one call.list_zonesList traffic-source zones (status / name filter, pagination, linked source).list_teamList team members (email, role, manager). **Never returns API tokens.create_team_memberInvite a team member (owner, manager, publisher, advertiser, publisher_manager, advertiser_manager). A scoped manager key can only create its own managed role, self-assigned. Returns the new API key **once** — `list_team` never shows it again. **Dry-run by default**; `confirm: true` to apply.create_campaignCreate a campaign from an advertiser email, offer URL, geo, payout and name. Defaults: CPA / rate 0, **paused**, global payout rule, and a ready tracking link (linked source template when configured; otherwise `source_click_id={clickid}` + sub placeholders). **Dry-run by default**; `confirm: true`…set_campaign_statusRun** or **pause** a campaign (`action: "run" \update_campaignPartial update (name, offer URL, status, rate, budgets, dates, …). **Dry-run by default**; `confirm: true` to apply. Prefer `set_campaign_status` for run/pause.create_zoneCreate a traffic-source zone (name + optional postback/site/traffic-back URLs, optional `traffic_source_id` link). Always created `active`. **Dry-run by default**; `confirm: true` to apply.update_zonePartial update (name, status, URLs, `traffic_source_id`). **Dry-run by default**; `confirm: true` to apply. Pass `null` to clear a URL or unlink the source.- +19 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AdButler
{
"mcpServers": {
"adbutler": {
"command": "npx",
"args": [
"-y",
"@adbutler/mcp-server"
],
"env": {
"ADBUTLER_API_KEY": "YOUR_ADBUTLER_API_KEY_HERE"
}
}
}
}
Affset
{
"mcpServers": {
"affset": {
"command": "npx",
"args": [
"-y",
"@affset/mcp"
]
}
}
}
Frequently asked questions
AdButler is categorized under Marketing and uses a local stdio subprocess. Affset belongs to Marketing and uses a local stdio subprocess. Pick AdButler for marketing work and Affset for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AdButler has no declared pricing — check the project's own site. Affset has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add adbutler and affset as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AdButler has a quality signal of 59/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Affset has 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars.