Snap them into your own AI harness with one command. They run locally, so you can audit a client's ad account without uploading a single row.
Add to your harness. No account.
Nothing uploaded. Your files stay yours.
No card. Pro unlocks offline.
Every one is the same shape: zero dependencies, runs locally, one command to install.
Give your AI a professional Meta Ads audit. The free tier scores an export 0–100 against cited 2026 benchmarks. Pro runs the full 8-section audit a media buyer would charge for: account-vs-benchmark, signal-quality checks, structure & creative volume, over-segmentation, reclaimable spend with a ranked kill/scale list, creative-fatigue lifecycle, and a 7-day plan — every finding tied to a real benchmark and the exact £.
claude mcp add ads-auditor -- node /path/to/ads-auditor/mcp/server.jsThen ask: "audit my ad account, the export is at ~/Downloads/ads.csv"
A professional Google Ads audit from a CSV — signal-quality first: broken conversion tracking, then relevance vs the 2026 3.41% search-CTR benchmark, zero-conversion waste with the exact campaigns, CPA outliers, concentration, naming, and priority actions. Every finding cited.
claude mcp add google-ads-auditor -- node /path/to/google-ads-auditor/mcp/server.jsThen ask: "audit my google ads, the export is at ~/Downloads/gads.csv"
Catches the tracking mistakes that silently split your analytics: missing utm_source / medium / campaign, uppercase, spaces, empty values, mixed separators, duplicate URLs, and an inconsistent vocabulary (Google vs google, cpc vs ppc vs paid).
claude mcp add utm-linter -- node /path/to/utm-linter/mcp/server.jsThen ask: "lint these tracking links" and paste them.
A signal-quality audit of a saved landing page — the #1 2026 paid-media lever. Beyond pixels and consent, it checks event dedup, advanced matching / Enhanced Conversions (Event Match Quality), server-side/CAPI signals, and untracked forms. It's the exact layer the Ads Auditors tell you to verify. Local file only — no crawl, no upload.
claude mcp add tracking-checker -- node /path/to/tracking-checker/mcp/server.jsThen ask: "check the tracking on ~/Downloads/landing.html"
More pluggable tools are on the way. Each one is the same shape: zero dependencies, runs locally, free.
Run against a live export. Nothing left the machine. This is the actual output, abridged.
╔══ Ads Auditor PRO — professional audit ══╗
Scope: £660 · 2 campaigns · 3 ad sets · 6 ads · 47 results · target CPA £8
1 · ACCOUNT vs 2026 BENCHMARK
Link-CTR 1.33% vs 2.19% median ▼ 39% below
CPA £14 vs £8 target ▲ 76% over
3 · STRUCTURE & CREATIVE VOLUME
[HIGH] 1 ad set rides a SINGLE ad — no bench; Andromeda needs 3-5 variants.
5 · WASTE — reclaim now
RECLAIMABLE: £450 (68% of spend)
• Zombie A — £180 · 0 results · ≥3× CPA → kill now (Meta 2026)
• Weak CTR C — CTR 0.60% < 0.8% floor → rotate creative
7 · SCALE — fund next
• Winner Hook B — CPA £6 (22 results, CTR 2.40%)
Benchmarks: 2026 Meta — CTR 2.19% / rotate <0.8%; freq cliff 4.0; kill 3× CPA.
Runs 100% locally — your data never left this machine.If you use Claude Code (or a similar local AI agent), you already have one — these tools plug straight into it. If you don't yet, that's the thing to set up first, and these tools are a reason to.