Ext Ops Panel
Open dashboard
Comparison

io.github.chiranj/mcp vs io.github.gudlab/ads-mcp

io.github.chiranj/mcp is an MCP server published by chiranj. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.gudlab/ads-mcp is an MCP server published by gudlab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceio.github.chiranj/mcpio.github.gudlab/ads-mcp
Official MCP Registry Listed, marked deprecated
Version: 0.2.4
Downloads/month (npm): 3 800
Downloads/week (npm): 750
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 371
Downloads/week (npm): 29
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

io.github.chiranj/mcp vs io.github.gudlab/ads-mcp
Factio.github.chiranj/mcpio.github.gudlab/ads-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-20Not published
Where it runs (differs)Remote server or your machineOn your machine (@gudlab/ads-mcp)
Transport (differs)stdio, Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 110, secrets among them: 6
LicenceNot statedNot stated
Repository (differs)github.com/vibeads/mcpgithub.com/gudlab/ads-mcp
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

io.github.chiranj/mcp

In its own words, on Official MCP Registry:

Manage Google Ads from Claude: read metrics, draft campaigns, publish with human approval.

io.github.gudlab/ads-mcp

In its own words, on Official MCP Registry:

MCP server for Google Ads and Meta Ads. Wraps both APIs directly to manage campaigns.

How to run each

io.github.chiranj/mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "VIBEADS_API_KEY=<YOUR_VIBEADS_API_KEY>" --transport stdio io-github-chiranj-mcp -- npx -y @vibeads/mcp

Requires: VIBEADS_API_KEY (secret)

io.github.gudlab/ads-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_ADS_CLIENT_ID=<YOUR_GOOGLE_ADS_CLIENT_ID>" --env "GOOGLE_ADS_CLIENT_SECRET=<YOUR_GOOGLE_ADS_CLIENT_SECRET>" --env "GOOGLE_ADS_CUSTOMER_ID=<YOUR_GOOGLE_ADS_CUSTOMER_ID>" --env "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" --env "GOOGLE_ADS_REFRESH_TOKEN=<YOUR_GOOGLE_ADS_REFRESH_TOKEN>" --env "META_ACCESS_TOKEN=<YOUR_META_ACCESS_TOKEN>" --env "META_AD_ACCOUNT_ID=<YOUR_META_AD_ACCOUNT_ID>" --env "META_APP_ID=<YOUR_META_APP_ID>" --env "META_APP_SECRET=<YOUR_META_APP_SECRET>" --transport stdio ads-mcp -- npx -y @gudlab/ads-mcp

Requires: GOOGLE_ADS_CLIENT_ID (secret), GOOGLE_ADS_CLIENT_SECRET (secret), GOOGLE_ADS_CUSTOMER_ID, GOOGLE_ADS_DEVELOPER_TOKEN (secret), GOOGLE_ADS_REFRESH_TOKEN (secret), META_ACCESS_TOKEN (secret), META_AD_ACCOUNT_ID, META_APP_ID, META_APP_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.chiranj/mcp asks for

  • VIBEADS_API_KEY (secret)

Only io.github.gudlab/ads-mcp asks for

  • GOOGLE_ADS_CLIENT_ID (secret)
  • GOOGLE_ADS_CLIENT_SECRET (secret)
  • GOOGLE_ADS_CUSTOMER_ID
  • GOOGLE_ADS_DEVELOPER_TOKEN (secret)
  • GOOGLE_ADS_LOGIN_CUSTOMER_ID
  • GOOGLE_ADS_REFRESH_TOKEN (secret)
  • META_ACCESS_TOKEN (secret)
  • META_AD_ACCOUNT_ID
  • META_APP_ID
  • META_APP_SECRET (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.chiranj/mcp · What it can do: io.github.gudlab/ads-mcp · 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.

Where the data comes from: how the catalog is built