ASO Atlas vs Meta Ads MCP
A side-by-side look at the ASO Atlas 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 ASO Atlas for marketing work over a hosted endpoint; 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 ASO Atlas when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_tracked_apps, get_dashboard, get_app.
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 | Remote HTTP/SSE | 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 | 91 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 17 | 134 |
| Full listing | View ASO Atlas | View Meta Ads MCP |
Tools & capabilities
ASO Atlas tools 17
list_tracked_appsThe apps you track, with the ids the other tools takeget_dashboardPer-app top 10 / top 50 counts, visibility trend, biggest movesget_appOne app in depth: keywords with rank, popularity, difficulty; competitors; keyword gapget_app_optimizerMetadata analysis for one storefront: coverage, missing terms, character budgetsget_app_performanceApp Store Connect digest: funnel, monetization, health, territoriesget_performance_seriesDaily history of one App Store Connect metric, optionally split by dimensionresearch_keywordsPopularity, difficulty and result count for up to 50 terms in a storefrontapp_ranking_keywordsReverse lookup: what any App Store app ranks forkeyword_suggestionsAutocomplete ideas for a seed termlist_keyword_listsSaved research collectionstrack_appStart or stop tracking an appadd_keywordsTrack or drop keywords per storefront- +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.
ASO Atlas
{
"mcpServers": {
"aso-atlas": {
"url": "https://asoatlas.com/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
ASO Atlas is categorized under Marketing and uses a remote HTTP/SSE transport. Meta Ads MCP belongs to Marketing and uses a local stdio subprocess. Pick ASO Atlas 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.
ASO Atlas 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 aso-atlas and mikusnuz-meta-ads-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ASO Atlas has a quality signal of 52/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Meta Ads MCP has 68/100 (Great) with 2 views, 0 installs and 91 GitHub stars.