Amazonads MCP vs GEO MCP
A side-by-side look at the Amazonads MCP and GEO MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Amazonads MCP for marketing work; choose GEO MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amazonads MCP when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
AMAZON_ADS_CLIENT_ID, AMAZON_ADS_CLIENT_SECRET, AMAZON_ADS_REFRESH_TOKEN, AMAZON_ADS_REGION, AMAZON_ADS_SANDBOX.
Choose GEO MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 29/100 · Emerging | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | AMAZON_ADS_CLIENT_IDAMAZON_ADS_CLIENT_SECRETAMAZON_ADS_REFRESH_TOKENAMAZON_ADS_REGIONAMAZON_ADS_SANDBOX | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 5,505 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Amazonads MCP | View GEO MCP |
Tools & capabilities
Amazonads MCP tools
No tool names declared yet. Check the project README from the listing page.
GEO MCP 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.
Amazonads MCP
No confirmed install command for Amazonads MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
GEO MCP
{
"mcpServers": {
"google-ads-meta-ads-seo-geo-mcp": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}