X Ads vs Meta Ads MCP
A side-by-side look at the X Ads 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 X Ads 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 X Ads when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
X_ADS_ACCESS_TOKEN, X_ADS_ACCOUNT_IDS, X_ADS_SCOPES, X_ADS_ENABLE_WRITES. - You want tools like
x_ads_list_ads_accounts, x_ads_list_campaigns, x_ads_get_campaign.
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 | 55/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 | X_ADS_ACCESS_TOKENX_ADS_ACCOUNT_IDSX_ADS_SCOPESX_ADS_ENABLE_WRITES | META_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 91 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 44 | 134 |
| Full listing | View X Ads | View Meta Ads MCP |
Tools & capabilities
X Ads tools 44
x_ads_list_ads_accountsList the ads accounts the authenticated user can accessx_ads_list_campaignsList campaigns for an accountx_ads_get_campaignGet a single campaign by IDx_ads_list_funding_instrumentsList funding instruments (payment sources) for an ads accountx_ads_list_line_itemsList line items (ad groups) for an ads accountx_ads_get_line_itemGet a single line item by IDx_ads_list_promoted_postsList promoted posts (promoted tweets) for an ads accountx_ads_list_targeting_criteriaList targeting criteria for an ads account's line itemsx_ads_list_account_postsList posts (tweets) usable for promotion by an ads accountx_ads_list_web_event_tagsList the website conversion event tags (pixels) in an ads account; a tag's id is what a conversion line item takes as its primary_web_event_tagx_ads_list_line_item_placementsList valid placement combinations per line item product typex_ads_get_account_statsGet synchronous analytics (impressions, engagements, spend) for an ads account- +32 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.
X Ads
{
"mcpServers": {
"x-ads": {
"command": "npx",
"args": [
"-y",
"@getmcpads/x-ads-mcp-server"
],
"env": {
"X_ADS_ACCESS_TOKEN": "YOUR_X_ADS_ACCESS_TOKEN_HERE",
"X_ADS_ACCOUNT_IDS": "YOUR_X_ADS_ACCOUNT_IDS_HERE",
"X_ADS_SCOPES": "YOUR_X_ADS_SCOPES_HERE",
"X_ADS_ENABLE_WRITES": "YOUR_X_ADS_ENABLE_WRITES_HERE"
}
}
}
}
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
X Ads is categorized under Marketing and uses a local stdio subprocess. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick X Ads 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.
X Ads 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 x-ads and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, X Ads has a quality signal of 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars.