Google Ad Manager MCP

What MatiousCorp/google-ad-manager-mcp MCP server does

MatiousCorp/google-ad-manager-mcp MCP server connects MCP-compatible AI clients to the Google Ad Manager SOAP API. Its tools cover the main objects involved in ad operations: advertisers, orders, line items, and creatives. The server can retrieve records, create new records, update selected properties, and perform workflow actions such as pausing, resuming, archiving, and approving line items.

The available operations support both individual and grouped workflows. For example, an agent can find or create an advertiser or order, create a line item, upload an image creative, and associate that creative with the line item. Creative tools also support uploading every creative from a folder, creating third-party HTML or JavaScript creatives, and generating a preview URL.

How it works

The server runs as a Python package and uses FastMCP as its MCP framework, with the Google Ad Manager Python client handling API access. Stdio is the default transport for local client configurations. HTTP mode is also available and exposes the MCP endpoint at /mcp; host and port values can be configured for deployments outside the local machine.

A single process can target multiple Ad Manager networks. Set the network codes as a comma-separated list, and the first code becomes the default. Tools accept an optional network_code parameter when an operation should use another configured network. The same service account credentials are used across those networks, so that account must have access to each one.

Setup and configuration

Install the package from PyPI with pip install google-ad-manager-mcp, or run it through uvx in an MCP client configuration. The required configuration consists of GAM_CREDENTIALS_PATH, pointing to a service account JSON file, and GAM_NETWORK_CODES, containing one or more Ad Manager network codes. The README also shows singular GAM_NETWORK_CODE in some run and container examples, but the configuration table identifies the plural variable as required.

GAM_MCP_TRANSPORT selects stdio or http and defaults to stdio. HTTP deployments can set GAM_MCP_HOST and GAM_MCP_PORT. For remote use, GAM_MCP_AUTH_TOKEN sets a fixed bearer token. If it is not set, the server generates a token at startup and writes it to the logs. Clients using authenticated HTTP must send the token in the Authorization: Bearer header.

Tools and capabilities

MatiousCorp/google-ad-manager-mcp MCP server provides tools for:

• Listing delivering orders and retrieving or creating orders.
• Finding, creating, duplicating, updating, and listing line items.
• Changing line-item state through pause, resume, archive, and approval actions.
• Uploading image creatives individually or from a folder, then associating them with line items.
• Creating third-party creatives with HTML or JavaScript ad tags.
• Finding, listing, retrieving, and creating advertisers.
• Checking line-item setup and delivery progress.

The line-item update operation covers properties such as name, type, delivery rate, priority, cost, goal, and end date. Creative updates can change a destination URL or name.

Limitations and notes

Access depends on valid Google Ad Manager service account credentials and the account's permissions in the target network. The server is an API control layer rather than an independent ad platform; it does not provide its own advertiser, order, or creative data. HTTP authentication is described for remote deployments, while local stdio configurations do not require that bearer-token flow.

The project is distributed under the MIT license and targets Python 3.10 or newer. Docker deployment is supported through the repository's Dockerfile, but container users still need to provide credentials and network configuration.