Meta Ads MCP vs X402 API
A side-by-side look at the Meta Ads MCP and X402 API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Meta Ads MCP for marketing work as a local process; choose X402 API 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 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.
Choose X402 API when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 68/100 · Great | 33/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | META_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 134 | Not listed |
| Full listing | View Meta Ads MCP | View X402 API |
Tools & capabilities
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
X402 API tools
No tool names declared yet. Check the project README from 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.
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"
}
}
}
}
X402 API
{
"mcpServers": {
"x402-api-2": {
"command": "uvx",
"args": [
"x402"
]
}
}
}
Frequently asked questions
Meta Ads MCP is categorized under Marketing and uses a local stdio subprocess. X402 API belongs to Marketing and uses a local stdio subprocess. Pick Meta Ads MCP for marketing work and X402 API 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.
Meta Ads MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. X402 API 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 mikusnuz-meta-ads-mcp and x402-api-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Meta Ads MCP has a quality signal of 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars. X402 API has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.