Adops MCP vs Meta Ads MCP
A side-by-side look at the Adops MCP 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 Adops MCP for marketing work; 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 Adops MCP when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
ADOPS_DATA_DIR. - You want tools like
ad_demo_seed, ad_csv_import, ads_export_recommendations.
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 | 43/100 · Fair | 68/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | ADOPS_DATA_DIR | META_ADS_ACCESS_TOKENMETA_AD_ACCOUNT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 84 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 17 | 134 |
| Full listing | View Adops MCP | View Meta Ads MCP |
Tools & capabilities
Adops MCP tools 17
ad_demo_seedSeed a realistic cross-platform demo portfolio (8 campaigns, 30 days of metrics) to try AdOps before importing real dataad_csv_importImport a Google Ads or Meta Ads CSV export** — every other tool operates on this dataads_export_recommendationsExport budget_analyze recommendations** as Google Ads Editor CSV, Meta Ads Manager CSV, JSON, or Markdown — one bulk-paste and your ad dashboard reflects the AI's planplatform_connectRegister a data source connection manually (alternative to CSV import, for scripted workflows)campaign_listList and filter campaigns across all imported platformscampaign_createAdd a campaign manually (useful for what-if planning)campaign_updateUpdate campaign settings in local storage (budget, status, bidding, schedule)campaign_pause_resumeBatch pause or resume up to 50 campaignsads_reportGenerate unified cross-platform performance reportbudget_analyzeAnalyze budget allocation, produce scaling/pausing recommendationsbudget_reallocateTransfer budget between campaigns across platformsaudience_insightsDemographic / geographic / device breakdowns- +5 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.
Adops MCP
No confirmed install command for Adops MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
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
Adops MCP is categorized under Marketing and uses an install path we have not confirmed yet. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick Adops MCP 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. Adops MCP has no confirmed install command yet — follow its own setup instructions.
Adops MCP 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 adops-mcp and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Adops MCP has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 84 GitHub stars.