Ext Ops Panel
Open dashboard
Comparison

Audiense Insights vs Camberstack: Google Ads

Audiense Insights is an MCP server published by AudienseCo. Marketplaces we read that list it: 1 (Docker MCP Catalog). Camberstack: Google Ads is an MCP server published by camberstack.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
MarketplaceAudiense InsightsCamberstack: Google Ads
Docker MCP Catalog Listed
Version: sha256:064623a07a6b
Forks (GitHub): 11
Pulls (Docker Hub): 41 251
Stars (Docker Hub): 0
Stars (GitHub): 19
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.15.0
Forks (GitHub): 0
Stars (GitHub): 0
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

Audiense Insights vs Camberstack: Google Ads
FactAudiense InsightsCamberstack: Google Ads
Marketplaces that list it11
Stars (GitHub) (differs)19 (better)0 (worse)
Pulls (Docker Hub) (differs)41 251No figure on Docker Hub
Forks (GitHub) (differs)11 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/audiense-insights)Remote server (camberstack.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)8Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/audienseco/mcp-audiense-insightsgithub.com/zwznco/camberstack-mcp
Changes in the last 7 days (differs)07
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

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

Audiense Insights

In its own words, on Docker MCP Catalog:

Audiense Insights MCP Server is a server based on the Model Context Protocol (MCP) that allows Claude and other MCP-compatible clients to interact with your Audiense Insights account.

Camberstack: Google Ads

In its own words, on Official MCP Registry:

Hosted Google Ads MCP: build Search, PMax, Display and YouTube campaigns, approve each change, undo.

How to run each

Audiense Insights As a local MCP server: Docker image

Claude Code
claude mcp add --env "AUDIENSE_CLIENT_SECRET=<YOUR_AUDIENSE_CLIENT_SECRET>" --env "TWITTER_BEARER_TOKEN=<YOUR_TWITTER_BEARER_TOKEN>" --transport stdio audiense-insights -- docker run -i --rm -e AUDIENSE_CLIENT_SECRET -e TWITTER_BEARER_TOKEN mcp/audiense-insights

Requires: AUDIENSE_CLIENT_SECRET (secret), TWITTER_BEARER_TOKEN (secret)

Camberstack: Google Ads As a remote MCP server

Claude Code
claude mcp add --transport http google-ads https://camberstack.io/mcp

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

The marketplaces of Camberstack: Google Ads publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Camberstack: Google Ads publish no settings it asks for, so we do not compare settings.

What it can do: Audiense Insights · What it can do: Camberstack: Google Ads · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built