A2db vs AdCrunch
A side-by-side look at the A2db and AdCrunch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose A2db for databases work; choose AdCrunch for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose A2db when
- You need dedicated capabilities in the Databases domain.
- You have the keys it needs:
DB_PASSWORD. - You want tools like
login, logout, list_connections.
Choose AdCrunch when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_advertisers, list_campaigns, list_ad_groups.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Social Media |
| Quality signal | 41/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DB_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | 8 |
| Full listing | View A2db | View AdCrunch |
Tools & capabilities
A2db tools 5
loginSave a connection — validates by connecting firstlogoutRemove a saved connectionlist_connectionsList connections (no secrets exposed)executeRun named batch queries with paginationsearch_objectsExplore schema — tables, columns, with detail levels
AdCrunch tools 8
list_advertisersConnected ad accounts across platformslist_campaignsCampaigns for an advertiserlist_ad_groupsAd-group structurelist_adsIndividual adsquery_insightsTime-series performance: spend, ROAS, CPA, impressions, clicks, conversionssearch_adsSearch ad creativeskill_listDiscover and fetch your org's reusable ad-ops playbooksskill_createAuthor and maintain playbooks (Skills store)
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.
A2db
No confirmed install command for A2db yet — follow the setup steps linked from its listing page rather than a guessed package name.
AdCrunch
{
"mcpServers": {
"adcrunch": {
"url": "https://mcp.adcrunch.dev/mcp"
}
}
}
Frequently asked questions
A2db is categorized under Databases and uses an install path we have not confirmed yet. AdCrunch belongs to Social Media and uses a remote HTTP/SSE transport. Pick A2db for databases work and AdCrunch for social media.
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. A2db has no confirmed install command yet — follow its own setup instructions.
A2db has no declared pricing — check the project's own site. AdCrunch 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 a2db and adcrunch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, A2db has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. AdCrunch has 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars.
