If you build landing pages, ad-tech, or marketing sites, your coding assistant already writes the copy and the components. It just has no idea what's actually working in the market. The AdWhispr MCP server fixes that — it drops real, verified Meta competitor ad data straight into Claude Code, Codex, or any MCP-capable CLI, so your assistant references proven winners instead of guessing.
This is a setup tutorial. In about five minutes you'll have the AdWhispr MCP Claude Code integration live, all 8 tools confirmed, and a quick test query running.
What you're connecting to
AdWhispr is Meta competitor-ad research over a chat interface and an MCP server. You point it at a brand's Facebook page; it ingests that brand's entire Meta ad library, snapshots it daily, and exposes the result as tools your assistant can call. The data is read-only — AdWhispr never touches anyone's live ad account and never launches campaigns. It only reads what's public in the Meta Ad Library and layers derived intelligence on top.
The single most useful signal it surfaces: days-running. Meta's API returns no run-time history, so AdWhispr builds it from daily snapshots. An ad live 100+ days is a proven winner, because no brand keeps paying to run a loser. That history is the product.
Two ways to connect
| Method | Best for | How |
|---|---|---|
| OAuth | Claude.ai, hosted MCP clients | Add server URL https://adwhispr.com/api/mcp |
| CLI config | Claude Code, Codex, local terminal tools | npx adwhispr-mcp-server config |
For terminal-based assistants — Claude Code CLI and Codex — the CLI route is the fast path. It writes the right config block for you so you don't hand-edit JSON.
Step 1 — Run the config helper
From any terminal:
npx adwhispr-mcp-server config
The npm package is unscoped — it's adwhispr-mcp-server, not @adwhispr/anything. The helper prints (or writes) the MCP server entry your client expects, pointing at the hosted endpoint:
https://adwhispr.com/api/mcp
You'll authenticate with your AdWhispr account on first connect. If you don't have one yet, the free tier ($0) gets you 1 brand and 5 messages a month — enough to confirm the integration works before you decide to upgrade.
Step 2 — Register the server with Claude Code
Claude Code reads MCP servers from its config. Add the AdWhispr entry:
claude mcp add adwhispr -- npx adwhispr-mcp-server
Or, if you prefer the hosted HTTP endpoint directly:
claude mcp add --transport http adwhispr https://adwhispr.com/api/mcp
Restart your Claude Code session so it picks up the new server, then run:
claude mcp list
You should see adwhispr listed and connected.
Step 3 — Wire it into Codex
Codex resolves MCP servers from its config file. Open your Codex MCP config and add:
[mcp_servers.adwhispr]
command = "npx"
args = ["adwhispr-mcp-server"]
Or run npx adwhispr-mcp-server config and paste the emitted block. Reload Codex and the tools register automatically. The same pattern works for most MCP-capable CLIs — the server itself is client-agnostic; only the config syntax differs.
Step 4 — Confirm the 8 tools
Whichever client you used, you should now have these 8 tools available:
search_brands— find tracked brands by name.get_brand_ads— pull a brand's ads, sortable by days-running.get_brand_stats— longevity, format mix, iteration rate for a brand.search_ads— semantic search across ad creative and copy.add_brand— kick off ingestion for a new Facebook page.compare_brands— side-by-side strategy diff across brands.clone_ad— generate original creative grounded in a real winner.generate_brief— export a competitive brief as PDF or Markdown.
Ask your assistant to list its tools, or just prompt: "Use the adwhispr tools to add Liquid Death and show me their longest-running ads." If add_brand and get_brand_ads fire and return data, you're done.
Why a developer wants this in their terminal
Pulling competitor ad data into a coding assistant isn't a novelty — it's a shortcut to better output on real work:
- Ad landing pages. Building a page for a paid campaign? Ask for the hooks and offers a competitor has run longest, and write copy that's grounded in what's converting rather than a blank page.
- Ad-tech and marketing sites. When your product is about ads, having the live market taxonomy — hook, format, tone, offer — one tool call away keeps your demos, seed data, and feature work honest.
- Cloning a proven structure.
clone_adtakes a verified winner and returns original assets: image ads become a new generated image in your brand identity, video ads become a scene-by-scene script and shot list. Always original, always grounded in a real ad, always citing the source. - Briefs without leaving the shell.
generate_briefleads with derived intelligence — longevity curve, engagement-verified reach, iteration rate — then the qualitative read. Pipe it to Markdown and drop it straight in your repo or PR.
The honesty rule (it matters here)
One thing your assistant will not do with these tools: invent metrics. The Meta Ad Library does not expose CTR, CPC, CPM, clicks, conversions, revenue, or ROAS for competitor ads — those live only inside the advertiser's account. Any tool that hands you a competitor's exact ROAS made it up.
AdWhispr instead cites the inputs behind every signal. Spend and impressions come as wide ranges, narrowed by engagement-verified reach (Meta's impression range cross-referenced with scraped likes, comments, and shares) and creative-iteration rate. When your coding assistant references this data, it's referencing something real — which is the whole point of bringing it into your workflow.
Troubleshooting
- Tools don't appear. Restart the client fully after adding the server; MCP servers load at startup.
- Auth loop. Make sure you completed the OAuth/login step on first connect. Free-tier accounts work fine for testing.
npxcan't find the package. Confirm the exact nameadwhispr-mcp-server— no scope, no typo.- Rate limits. Free is 5 messages/month. Pro ($29/mo) unlocks unlimited tool calls and 3 brands; Agency ($149/mo) adds cross-brand comparison and 10+ brands.
That's the whole setup. Once it's live, your terminal assistant stops guessing about the ad market and starts reading from it. See more guides on the AdWhispr blog, or spin up an account at adwhispr.com.
Connect the MCP server once, and every landing page you ship gets competitor intelligence baked in.