adwarp

Start with 1 prompt.

Paste it into Claude Code, Codex or Cursor. Your agent installs Adwarp, walks you through your LinkedIn app and checks the connection.

setup prompt
Set up Adwarp for me. It's the open-source ad agent for LinkedIn Ads and Google Ads: https://github.com/adwarp-dev/adwarp

1. Check that Node.js 20 or newer is installed.
2. Walk me through creating my own LinkedIn developer app with the Advertising API product: https://github.com/adwarp-dev/adwarp/blob/main/docs/linkedin-app.md
3. Save the app's client ID and secret to ~/.adwarp/config.json as clientId and clientSecret.
4. Run "npx -y adwarp auth login" and wait while I approve access in my browser.
5. Add Adwarp to the AI client I'm using right now as an MCP server that runs "npx -y adwarp mcp". In Claude Code that's: claude mcp add adwarp -- npx -y adwarp mcp
6. Check the connection by listing my ad accounts, then save the one I pick as defaultAccountId in ~/.adwarp/config.json.

Don't create or change anything in my ad accounts during setup. LinkedIn campaigns start as drafts, so nothing spends until I turn it on.
adwarp
GitHub

Start with 1 prompt.

Paste it into Claude Code, Codex or Cursor. Your agent installs Adwarp, walks you through your LinkedIn app and checks the connection.

setup prompt
Set up Adwarp for me. It's the open-source ad agent for LinkedIn Ads and Google Ads: https://github.com/adwarp-dev/adwarp

1. Check that Node.js 20 or newer is installed.
2. Walk me through creating my own LinkedIn developer app with the Advertising API product: https://github.com/adwarp-dev/adwarp/blob/main/docs/linkedin-app.md
3. Save the app's client ID and secret to ~/.adwarp/config.json as clientId and clientSecret.
4. Run "npx -y adwarp auth login" and wait while I approve access in my browser.
5. Add Adwarp to the AI client I'm using right now as an MCP server that runs "npx -y adwarp mcp". In Claude Code that's: claude mcp add adwarp -- npx -y adwarp mcp
6. Check the connection by listing my ad accounts, then save the one I pick as defaultAccountId in ~/.adwarp/config.json.

Don't create or change anything in my ad accounts during setup. LinkedIn campaigns start as drafts, so nothing spends until I turn it on.

Terms of service

Adwarp is free, open-source software you run against your own ad accounts. These terms cover what that means for you.

Last updated

What these terms cover

These terms cover adwarp.dev, the adwarp CLI and MCP server you run on your own computer, and the hosted endpoint at mcp.adwarp.dev. Using any of them means you accept these terms.

Adwarp is operated by its maintainer, Stan Rymkiewicz. It is unofficial and not affiliated with or endorsed by LinkedIn or Google. It calls their public APIs with credentials you supply.

The license

The code is open source under the MIT license. You can use, copy, change and share it on those terms, and self-host the endpoint. Where these terms and the license disagree about the code, the license wins.

Your accounts and apps

Adwarp has no ad accounts of its own. It runs against the ad accounts you connect, through a developer app you register with LinkedIn or Google and an OAuth grant you approve. Keep those credentials secret, and revoke them if they leak.

Use Adwarp only on accounts you own or are allowed to manage, and follow each platform's terms when you do, including the LinkedIn Marketing API terms and the Google Ads API Terms of Service. Where their terms conflict with these, theirs govern your use of their API. You are responsible for the contact lists you upload and the ads you run.

Ad spend

Nothing spends until you turn it on. LinkedIn campaign groups, campaigns and ads are created as drafts, and Google Ads campaigns, ad groups and ads are created paused. On LinkedIn, Adwarp sets a campaign or an ad live only when you ask it to. On Google, you turn campaigns on yourself in Google Ads.

You are responsible for every campaign you turn on, every budget you set and all spend on your accounts. Review what Adwarp built before you switch it on.

The hosted endpoint

The hosted endpoint is free and offered as a convenience, with no promise of uptime. It may change, limit requests or stop at any time without notice. If you need it to be reliable, self-host it.

Abuse, attempts to reach accounts you don't control, and use that degrades the endpoint for others are not allowed, and access may be withdrawn.

No warranty

Adwarp is provided as is, without warranty of any kind, as the MIT license says. It automates a system that spends money, and it can be wrong: an API can change, a report can mislead and a brief can be misread.

To the fullest extent the law allows, the maintainer and the other authors are not liable for any claim, damages or other liability arising from your use of Adwarp, including ad spend, lost revenue, lost data or campaigns that performed worse than you hoped. Check before you turn anything on.

Changes and contact

These terms may change. When they do, the date at the top changes too, and using Adwarp after a change means you accept it.

For questions about these terms, bugs or feature requests, open an issue at github.com/adwarp-dev/adwarp/issues.