# adwarp [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/adwarp-dev/adwarp  
**GitHub Stars:** 23  
**npm Downloads (last month):** 609  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/adwarp

## Description
Open-source ad agent for LinkedIn Ads and Google Ads. Drafts campaigns, audiences and reports from Claude or any MCP client.

## Tools
Capabilities this server exposes over MCP:

- **list_ad_accounts**
- **list_targeting_facets**
- **search_targeting**
- **list_facet_entities**
- **estimate_audience**
- **upload_audience_csv**
- **list_conversions**
- **create_campaign_group**
- **create_campaign**
- **create_text_ad**
- **create_image_ad**
- **launch_from_brief**
- **performance_summary**
- **get_performance**
- **inspect_competitor_ads**
- **log_ad_change**
- **list_ad_changes**
- **compute_lift**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "adwarp": {
    "command": "npx",
    "args": ["-y","adwarp"]
  }
}
```

## Documentation

## What adwarp does

adwarp provides an MCP interface for working with LinkedIn Ads and Google Ads. Its capabilities cover the campaign lifecycle: discovering ad accounts, finding targeting options, estimating audience size, uploading matched-audience data, selecting conversions, creating campaigns and ads, reviewing performance, and recording changes.

LinkedIn workflows include campaign groups, campaigns, text ads, image ads, matched audiences, conversion selection, and performance analysis. Audience data can come from CSV files, Salesforce contacts, or HubSpot lists and searches. The server can also inspect public competitor ads, including copy, formats, and EU targeting metadata.

Google Ads support is focused on search campaigns. A launch can create the budget, campaign, geographic and language targeting, ad groups, keywords, and responsive search ads together. Google campaign creation uses paused entities; LinkedIn campaign entities are drafts. The platform-specific hierarchy differs, so a LinkedIn campaign group and campaign do not map directly to a Google campaign and ad group.

## How it works

The primary interface is the `@adwarp/mcp` package, which runs over stdio for local use. The hosted web package also exposes MCP over HTTP at `https://mcp.adwarp.dev/api/mcp`. The same underlying engines are available through the `adwarp` CLI for scripts and batch jobs.

MCP requests can perform operations such as `launch_from_brief`, `performance_summary`, or `compute_lift`. Adwarp resolves the requested account and campaign details, performs the operation, and reports resulting IDs or analysis. Google launch operations validate the request server-side before applying changes and use one atomic mutation, avoiding a partially created campaign when the operation fails.

There is no built-in scheduler. Recurring reports, competitor checks, and audience-status checks must be scheduled by the client or an external system such as cron.

## Setup and configuration

Install and run the published npm package or use the hosted MCP endpoint. For local workflows, the package includes the `adwarp` and `adwarp-mcp` commands. The CLI and MCP server use the same platform engines.

Google Ads requires a developer token from a manager account and an OAuth desktop client from a Google Cloud project with the Google Ads API enabled. Store Google credentials in `~/.adwarp/google.json`, including the client ID, client secret, developer token, login customer ID when accessing an account through a manager, default customer ID, and optional default conversion action names. Complete authentication with `adwarp google auth login`.

Google keyword research requires Basic developer-token access; campaign creation and reporting work with Explorer access. A Google OAuth consent screen left in Testing produces refresh tokens that expire after seven days.

## Tools and capabilities

- `list_ad_accounts` lists accessible advertising accounts.
- `list_targeting_facets`, `search_targeting`, and `list_facet_entities` resolve targeting choices.
- `estimate_audience` forecasts reachable audience size before spending.
- `upload_audience_csv` cleans and transforms CSV audience data for matching.
- `list_conversions` retrieves available conversion actions.
- `create_campaign_group`, `create_campaign`, `create_text_ad`, and `create_image_ad` create LinkedIn campaign components.
- `launch_from_brief` creates a campaign workflow from a brief.
- `performance_summary` and `get_performance` retrieve performance analysis.
- `inspect_competitor_ads` reads public competitor advertising information.
- `log_ad_change`, `list_ad_changes`, and `compute_lift` support change history and before-and-after analysis.

## Limitations and notes

Google support currently covers search campaigns and creation-first workflows. Search network expansion, search partners, and audience expansion are disabled by the platform rules described for Google launches; bidding starts with manual CPC.

New campaigns are intentionally inactive: LinkedIn objects begin as drafts, and Google objects begin paused. LinkedIn campaigns can be enabled through an explicit request or Campaign Manager, while Google campaigns must be enabled in the Google Ads UI. Matched audiences need sufficient members before they can serve; the documented threshold is 300 members.

Adwarp is unofficial and is not affiliated with or endorsed by LinkedIn or Google.

_Full upstream README: https://allmcps.com/mcp/adwarp/readme_