Affset vs Meta Ads MCP
A side-by-side look at the Affset and Meta Ads MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Affset for marketing work as a local process; choose Meta Ads MCP 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 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.
Choose Meta Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
META_ADS_ACCESS_TOKEN, META_AD_ACCOUNT_ID. - You want tools like
list_campaigns, get_campaign, create_campaign.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 52/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | META_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 87 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 31 | 134 |
| Full listing | View Affset | View Meta Ads MCP |
Tools & capabilities
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
Meta Ads MCP tools 134
list_campaignsList campaigns in the ad account. Supports filtering by status and objective. Returns paginated results.get_campaignGet details of a specific campaign by ID.create_campaignCreate a new ad campaign. Defaults to PAUSED status. Requires name and objective. Budget can be set at campaign or ad set level.update_campaignUpdate an existing campaign. Only provided fields will be modified.delete_campaignDelete a campaign. This action is irreversible.copy_campaignCopy an existing campaign. Creates a duplicate with optional name override. Copies structure including ad sets and ads.get_campaign_adsetsGet all ad sets belonging to a specific campaign.get_campaign_adsGet all ads belonging to a specific campaign.get_campaign_leadsGet leads generated by a specific campaign. Requires leads_retrieval permission.list_adsetsList ad sets in the ad account. Optionally filter by campaign or status.get_adsetGet details of a specific ad set by ID.create_adsetCreate a new ad set. Requires name, campaign_id, budget, optimization_goal, billing_event, and targeting. Defaults to PAUSED status.- +122 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.
Affset
{
"mcpServers": {
"affset": {
"command": "npx",
"args": [
"-y",
"@affset/mcp"
]
}
}
}
Meta Ads MCP
{
"mcpServers": {
"mikusnuz-meta-ads-mcp": {
"command": "npx",
"args": [
"-y",
"@mikusnuz/meta-ads-mcp"
],
"env": {
"META_ADS_ACCESS_TOKEN": "YOUR_META_ADS_ACCESS_TOKEN_HERE",
"META_AD_ACCOUNT_ID": "YOUR_META_AD_ACCOUNT_ID_HERE"
}
}
}
}
Frequently asked questions
Affset is categorized under Marketing and uses a local stdio subprocess. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Affset for marketing work and Meta Ads MCP 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.
Affset has no declared pricing — check the project's own site. Meta Ads MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 affset and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Affset has a quality signal of 52/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 87 GitHub stars.