Camberstack: Google Ads vs Campaign Manager 360 MCP Server
Camberstack: Google Ads is an MCP server published by camberstack.io. Marketplaces we read that list it: 1 (Official MCP Registry). Campaign Manager 360 MCP Server is an MCP server published by cesteral. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Camberstack: Google Ads |  Campaign Manager 360 MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.17.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.3.0 Downloads/month (npm): 896 Downloads/week (npm): 101 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Camberstack: Google Ads | Campaign Manager 360 MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | Remote server (camberstack.io/mcp) | On your machine (@cesteral/cm360-mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/zwznco/camberstack-mcp | github.com/cesteral/mcp-open-advertising |
| Changes in the last 7 days (differs) | 5 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 32 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Camberstack: Google Ads
Hosted Google Ads MCP: build Search, PMax, Display and YouTube campaigns, approve each change, undo.
Campaign Manager 360 MCP Server
Campaign Manager 360 management — CRUD, Floodlight tracking, async reporting, and targeting
How to run each
Camberstack: Google Ads As a remote MCP server
claude mcp add --transport http google-ads https://camberstack.io/mcpCampaign Manager 360 MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Camberstack: Google Ads has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Camberstack: Google Ads · What it can do: Campaign Manager 360 MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.