In-depth architectural comparison of the Hub MCP and Walmart Connect Advertising APIs MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Hub MCP
Developer Tools · Remote HTTP/SSE
Quality: 77/100 (Great) | Auth: API Key required
Walmart Connect Advertising APIs
Developer Tools · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Hub MCP if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Walmart Connect Advertising APIs if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Hub MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: HUB_PAT_TOKEN, MCP_AUTH_TOKEN.
Hub MCP is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Walmart Connect Advertising APIs belongs to Developer Tools using local stdio subprocess. Select Hub MCP when you need capabilities focused on developer tools and Walmart Connect Advertising APIs when you require tools for developer tools.
Number of documents to skip for pagination (number, optional)
images
Filter on image names (string, optional)
operating_systems
Filter on operating systems (string, optional)
order
Change the ordering of results (string, optional)
size
Maximum number of results to return (number, optional)
sort
Sort results by search field (string, optional)
+23 more tools listed on main page
Walmart Connect Advertising APIs Tools (5)
list_endpoints
List operations from the bundled OpenAPI spec for an `ad_type`, with optional filters.
describe_endpoint
Return one operation plus the `components.schemas` reachable from it (its `$ref` closure), so request bodies and responses can be built without the full spec.
call_endpoint
Execute any Walmart Connect Ads API endpoint. Identify it by `operation_id`, or by raw `method` + `path`. Raw method+path also reaches alpha/beta/unpublished endpoints that are not in the bundled specs. The server handles RSA-SHA256 signing.
refresh_specs
Re-fetch the bundled OpenAPI specs from ReadMe's public api-registry into a user cache (`~/.cache/mcp-walmart-ads/specs/`) that takes precedence over the bundled copy.
download_display_snapshot
Download a display snapshot file (report or entity). Display snapshot URLs require authenticated requests, so this tool handles the signing automatically. Use the full download URL from the `details` field after polling a display snapshot to `done` status.
Walmart Connect Advertising APIs vs Openapi MCP Server