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.

Adwarp connects Salesforce, HubSpot, LinkedIn Ads and Google Ads.

Adwarp is an open-source MCP server and CLI that runs LinkedIn Ads and Google Ads from your terminal. Salesforce and HubSpot feed it audiences: a SOQL query, a HubSpot list or a CRM search becomes a LinkedIn matched audience.

$ claude mcp add adwarp -- npx -y adwarp mcp

Read the docs

01Integrations

2 data sources and 2 ad platforms. Each has its own page, with the tools behind it.

02Where it runs

Pick where you run it. The same tools in every MCP client, or straight from the CLI.

03Results

Why it gets better results.

  • Audiences from your CRM

    Lists come straight from Salesforce or HubSpot, so they're current the day you launch.

  • No export step

    No report export or CSV cleanup between your CRM and LinkedIn.

  • Data stays local

    CRM reads and list uploads run on your machine, and emails are hashed before they leave it.

04FAQ

Questions, answered. Before you install.

Ask on GitHub
Which integrations does Adwarp have?

Salesforce and HubSpot as data sources, plus LinkedIn Ads and Google Ads as ad platforms. It runs in Claude, Codex, Cursor or any MCP client, or as a CLI.

What credentials do Salesforce and HubSpot need?

Salesforce needs none of its own: Adwarp reuses your signed-in Salesforce CLI. HubSpot needs a private app token with 3 read-only scopes, kept on your machine. Both only read.

Do integrations work on the hosted endpoint?

Partly. The hosted endpoint serves LinkedIn tools only, and none of the Google tools. Salesforce and HubSpot audiences, CSV uploads and the change journal need your machine, so they run through the local MCP server or the CLI.

Is Adwarp free?

Yes. It's open source under the MIT license, and you only pay LinkedIn and Google for the ads you run.