Amazon Ads MCP vs Omneum
A side-by-side look at the Amazon Ads MCP and Omneum MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Amazon Ads MCPDeveloper Tools · Remote HTTP/SSEAmazon Ads API MCP server for Amazon Advertising API40FairAuth: not declaredO
OmneumDeveloper Tools · Local subprocess (stdio)Evaluate your agent's context for unreliable sources, dependencies, redundant and stale claims.40FairAuth: not declaredVerdict: choose Amazon Ads MCP for developer tools work over a hosted endpoint; choose Omneum 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?
Choose Amazon Ads MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
OChoose Omneum 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 | Amazon Ads MCP | O Omneum |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 72 | 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 Omneum |
Tools & capabilities
Amazon Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
Omneum 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/"
}
}
}
Omneum
{
"mcpServers": {
"omneum": {
"command": "uvx",
"args": [
"omneum"
]
}
}
}
Frequently asked questions
Amazon Ads MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Omneum belongs to Developer Tools and uses a local stdio subprocess. Pick Amazon Ads MCP for developer tools work and Omneum for developer tools.
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.
Amazon Ads MCP has no declared pricing — check the project's own site. Omneum 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 omneum 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 40/100 (Fair) with 2 views, 0 installs and 72 GitHub stars. Omneum has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.