Ext Ops Panel
Open dashboard
Comparison

ads-agent vs PaidSync.ai

ads-agent is a plugin bundle for AI coding tools published by nowork-studio. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). PaidSync.ai is an MCP server published by PaidSync. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplaceads-agentPaidSync.ai
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.3.1
Forks (GitHub): 1
Stars (GitHub): 4
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

ads-agent vs PaidSync.ai
Factads-agentPaidSync.ai
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)4 (better)
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.adsagent.org/api/mcp)Remote server (mcp.paidsync.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nowork-studio/adsagent-plugingithub.com/paidsync/paidsync-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 33 h ago, requires a key

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

ads-agent

In its own words, on Claude Code: claude-plugins-community:

AdsAgent turns Claude into your always-on Google Ads analyst. Audit account health, set up new campaigns from scratch, analyze Quality Score and Ad Rank, manage keywords and bids, mine search terms for negatives, generate A/B-tested ad copy, configure tracking, and run bulk operations across hundreds of keywords — all through conversation. No dashboards, no spreadsheets, no clicking through the Google Ads UI. Under the hood: 40+ MCP tools with full read/write access to your Google Ads data, plus three built-in skills — /ads for campaign management, /ads-audit for account health scoring, and /ads-copy for ad copywriting.

PaidSync.ai

In its own words, on Official MCP Registry:

Run ads on Google, Meta, LinkedIn, TikTok and more from AI. 610+ tools across 14 platforms.

How to run each

ads-agent As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install ads-agent@claude-community

PaidSync.ai As a remote MCP server

Claude Code
claude mcp add --transport http paidsync https://mcp.paidsync.ai/mcp

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

Only PaidSync.ai 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: ads-agent · What it can do: PaidSync.ai · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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