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.

LinkedIn Ads in Meta Muse

Adwarp is an open-source MCP server that connects Meta Muse to LinkedIn Ads. Run your own Adwarp endpoint, add it to Muse as a custom connector, then ask Muse to size audiences, draft campaigns and pull reports.

> Add a custom MCP server called adwarp at https://your-app.vercel.app/api/mcp

Read the docs

muse ~ draft

> Draft a LinkedIn campaign for VPs of demand gen at 50 USD a day.

adwarp.create_campaign "VP Demand Gen", 50 USD/day: DRAFT

adwarp.create_text_ad 3 variants: DRAFT

Nothing is live. Review them in Campaign Manager.

01Set up

Set up in 3 steps

  1. Sign in to LinkedIn once

    Create a LinkedIn developer app with the Advertising API, then sign in from your terminal. App approval usually takes a day or 2.

    npx -y adwarp auth login
  2. Deploy your own endpoint

    Muse runs in Meta's cloud, so it can't reach your laptop. Deploy Adwarp's endpoint in 1 click, and paste in the values npx -y adwarp auth export prints plus a token from openssl rand -hex 32.

  3. Add it in Muse

    Send Muse this message with your endpoint's URL. When it asks for a key, type your MCP_AUTH_TOKEN into the secure prompt as a bearer token, never into the chat.

    Add a custom MCP server called adwarp at https://your-app.vercel.app/api/mcp
Setting it up by hand?

The Deploy button asks for these. By hand, create a Vercel project from the Adwarp repo with its Root Directory set to apps/web and add them. If Vercel Authentication covers production, turn it off there, or Muse can't reach the endpoint.

Vercel environment variables
ADWARP_LINKEDIN_CLIENT_ID=...
ADWARP_LINKEDIN_CLIENT_SECRET=...
ADWARP_LINKEDIN_REFRESH_TOKEN=...
MCP_AUTH_TOKEN=<a long random string>

02Try these prompts

5 prompts to try first

muse ~ reach

> How many VPs of demand gen at US software companies can we reach on LinkedIn?

adwarp.estimate_audience titles + VP + US + software: 2,140 members

03Results

Why running LinkedIn ads from Muse gets better results

  • Meta and LinkedIn in 1 chat

    Muse reads your Meta ads through its own connector and Adwarp adds LinkedIn, so 1 question compares both.

  • Nothing spends on its own

    Every campaign and ad starts as a draft, and Muse can ask before every action, so you approve what goes live.

  • Your secret stays in Vercel

    Muse holds 1 token for your own endpoint. Your LinkedIn client secret stays in your Vercel project.

04FAQ

Questions, answered From setup to the details.

Ask on GitHub
Does Meta Muse connect to LinkedIn Ads?

Not on its own. Muse has no LinkedIn Ads connector, so Adwarp adds one: an open-source MCP server that reaches LinkedIn Ads through your own developer app.

Why do I need my own endpoint?

Muse runs in Meta's cloud, so it can't reach a server on your laptop. Your own endpoint takes 1 bearer token, which is how Muse adds a custom connector, and it keeps your LinkedIn client secret out of Muse.

Muse setup in the docs

Can Muse spend money on its own?

No. Every campaign, ad group and ad starts as a draft, and it goes live only when you explicitly ask or switch it on in Campaign Manager.

Does it work for Google Ads?

Not yet. Adwarp's Google tools run on your machine, which Muse can't reach.

Google Ads in Muse

Where are my LinkedIn credentials stored?

In your Vercel project's environment variables. Muse keeps only the bearer token for your endpoint, in its secure credential store.

Which tools work in Muse?

Every LinkedIn tool your endpoint serves: audience sizing, campaigns and ads, reporting and Ad Library search.

List uploads, CRM audiences and the change journal read files on your machine, so they run in Claude, Codex, Cursor or the CLI.

Which tools work in Muse?
FeatureIn Muse
Campaigns, audience sizing, reportingYes
Ad Library through the official APIYes
CSV list uploadsNo
Salesforce and HubSpot audiencesNo
Change journal and liftNo
What does Muse ask for?

A name, your endpoint's URL, the transport and 1 bearer token.

What does Muse ask for?
Muse asksAnswer
Nameadwarp
URLhttps://your-app.vercel.app/api/mcp
TransportHTTP
AuthBearer token: your MCP_AUTH_TOKEN, typed into the secure prompt