Adrex AI MCP Server

Open-source MCP server for Google Ads & Meta Ads — manage campaigns from any AI assistant.

Local serverstdio

What is the Adrex AI MCP server?

Adrex AI MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Open-source MCP server for Google Ads & Meta Ads — manage campaigns from any AI assistant.

What you get

Open-source MCP server for Google Ads & Meta Ads

Adrex AI is an open-source MCP (Model Context Protocol) server that connects AI assistants to your Google Ads account, with Meta Ads coming soon. Instead of navigating complex dashboards, you manage campaigns, reporting, keywords, and targeting through natural language — from Claude, Cursor, Codex, or any MCP client.

What the assistant can call

Once Adrex AI is connected, these are the calls the assistant has available:

  • Campaigns — The Campaigns tool exposed by this server
  • Keywords — The Keywords tool exposed by this server
  • Reporting — The Reporting tool exposed by this server

Setting it up

server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: ADREX_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Adrex AI's toolset — Campaigns, Keywords, Reporting — is a fair guide to whether it matches your workflow. It is maintained by gauravapiscean; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the adrex ai mcp server does with a few real requests.

Available tools

ToolWhat it does
CampaignsThe Campaigns tool exposed by this server.
KeywordsThe Keywords tool exposed by this server.
ReportingThe Reporting tool exposed by this server.

How to install the Adrex AI MCP server

{
  "mcpServers": {
    "adrex-ai": {
      "command": "npx",
      "args": ["-y", "adrex-ai"],
      "env": {
        "ADREX_API_KEY": "your-api-key"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ADREX_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Adrex AI to Campaigns.
  • Use Adrex AI to Keywords.
  • Use Adrex AI to Reporting.

Frequently asked questions

It connects Adrex AI to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Campaigns, Keywords, Reporting) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Adrex AI directly.