Appsflyer MCP vs Atlas
A side-by-side look at the Appsflyer MCP and Atlas MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Appsflyer MCP for marketing work; choose Atlas for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Appsflyer MCP when
- You need dedicated capabilities in the Marketing domain.
Choose Atlas when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Appsflyer MCP | |
|---|---|---|
| Category | Marketing | Developer Tools |
| Quality signal | 36/100 · Fair | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Appsflyer MCP | View Atlas |
Tools & capabilities
Appsflyer MCP tools
No tool names declared yet. Check the project README from the listing page.
Atlas 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.
Appsflyer MCP
No confirmed install command for Appsflyer MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Atlas
{
"mcpServers": {
"atlas-2": {
"command": "bunx",
"args": [
"@useatlas/mcp"
]
}
}
}