Amazon Ads MCP vs Yandex Metrica MCP
A side-by-side look at the Amazon Ads MCP and Yandex Metrica MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Amazon Ads MCPMarketing · Remote HTTP/SSEAmazon Ads API MCP server for Amazon Advertising API41FairAuth: not declaredY
Yandex Metrica MCPMarketingYandex Metrica for AI agents: counters, goals, Reporting API and Logs API export over stdio.33EmergingAuth: not declaredVerdict: choose Amazon Ads MCP for marketing work over a hosted endpoint; choose Yandex Metrica MCP for marketing. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amazon Ads MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
YChoose Yandex Metrica MCP when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
YANDEX_METRICA_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Amazon Ads MCP | Y Yandex Metrica MCP |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 41/100 · Fair | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | YANDEX_METRICA_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 73 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Amazon Ads MCP | View Yandex Metrica MCP |
Tools & capabilities
Amazon Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
Yandex Metrica 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.
Amazon Ads MCP
{
"mcpServers": {
"amazon-ads-mcp": {
"url": "http://localhost:9080/mcp/"
}
}
}
Yandex Metrica MCP
No confirmed install command for Yandex Metrica MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Amazon Ads MCP is categorized under Marketing and uses a remote HTTP/SSE transport. Yandex Metrica MCP belongs to Marketing and uses an install path we have not confirmed yet. Pick Amazon Ads MCP for marketing work and Yandex Metrica 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. Yandex Metrica MCP has no confirmed install command yet — follow its own setup instructions.
Amazon Ads MCP has no declared pricing — check the project's own site. Yandex Metrica MCP 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 amazon-ads-mcp and yandex-metrica-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Amazon Ads MCP has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 73 GitHub stars. Yandex Metrica MCP has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
