ads-mcp

Purpose: Connecting AI assistants to Google Ads and Meta Ads data and campaign operations.

Inferred · not functionally tested

Audience: developers and advertising automation teams

Inferred · not functionally tested

Functions: agents, data_extraction, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, ads-mcp takes a focused approach. Inferred · not functionally tested: It focuses on connecting AI assistants to Google Ads and Meta Ads data and campaign operations. Inferred · not functionally tested: ads-mcp is an open-source project aimed at developers and advertising automation teams. Basis unknown · not verified: The project is open source (Open Source). Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.

gudlab builds and maintains ads-mcp. PulseGate's similarity index places it among 5 comparable projects. Inferred · not functionally tested: Among its 5 catalogued features are Google Ads access, Meta Ads access, and MCP server. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.