Adwarp MCP server

Adwarp

Website · Docs · Install guide · npm package

Adwarp (formerly Liam) is the open-source ad agent for LinkedIn Ads and Google Ads. Create campaigns by talking to Claude (MCP) or from a CLI. Built for go-to-market teams who want to spin up many campaigns from a contact list and a brief, then add creative images themselves. Everything starts switched off: LinkedIn entities are created as drafts and Google entities as paused. A LinkedIn campaign goes live only when you explicitly ask Adwarp to turn it on or switch it on yourself in Campaign Manager, and Google campaigns can only be switched on in the Google Ads UI.

Unofficial and not affiliated with or endorsed by LinkedIn or Google.

Covers creation, matched audiences (including building one straight from Salesforce or HubSpot),

conversion selection, performance reporting/insights, competitor ad intelligence, and a

change journal with before/after lift. See ROADMAP.md for what's shipped

and what's planned next.

What you can do with it

Once Adwarp is connected, you talk to your assistant in plain language. Real requests it handles today, roughly in the order a campaign comes together:

facets, estimates reach before any money is involved)

• "How many VPs of demand gen at US SaaS companies can we reach?" (resolves targeting

companies and titles for LinkedIn's people match, converts company domains to URLs)

• "Upload this CSV as a matched audience." (auto-cleans columns, hashes emails, keeps names,

(SOQL straight to a matched audience)

• "Build an audience from Salesforce: every contact on an account flagged as a target."

straight to a matched audience of contacts or companies)

• "Turn our HubSpot target accounts list into a LinkedIn audience." (a HubSpot list or search

conversion." (campaign group + campaign + draft ads in one call)

• "Launch a draft campaign for that audience, $100/day, tracking the demo-booked

public Ad Library: copy, formats, and EU targeting metadata for any company)

• "What ads is our biggest competitor running right now, and what offers are they pushing?" (reads the

flags, then pauses the ads you pick, leaving the rest of each ad group running)

• "How did retargeting do last month vs the month before?" (trend report with deltas)
• "Which ads should I pause this week?" (account rollup with top/bottom performers and

ignores edits to a live ad's post)

• "Rewrite the copy on the losing ad." (delete + recreate as a fresh draft; LinkedIn

• "Did the new headline actually help?" (change journal + before/after lift)

Adwarp resolves the details and reports back the ids. Every capability is also an adwarp CLI command for scripted or batch use.

Put it on a loop

There is no scheduler in Adwarp. Use the one in whatever client you drive it from. Some loops that work well:

before, and flag anything that moved more than 20%." (a Claude Code scheduled agent)

• "Every Monday at 9am, pull last week's performance summary, compare it to the week

summarize the angles."

• "Every Friday, check what new ads our top three competitors shipped this week and

members." (the minimum for a matched audience to serve)

• "Check the audience match status every few hours and tell me when it clears 300

0 9 1 adwarp report summary -p last7days

• Or skip the assistant entirely and put the CLI in cron:

Hierarchy mapping (the two platforms disagree)

LinkedIn's names are shifted one level from everyone else's, which is the single most common source of confusion when working across both:

Shortened. The full README is on GitHub.