How to integrate Google Ads MCP with Mastra AI

Connect Mastra AI to Google Ads MCP. Create a new customer list for holiday campaigns, get campaign details by campaign id, and more using natural language, with authentication handled for you.

Google Ads logoGoogle Ads
Oauth2

Google Ads is Google's online advertising platform for creating, managing, and optimizing digital campaigns. It helps businesses reach targeted customers and maximize return on ad spend.

36 Tools

Introduction

This guide walks you through connecting Google Ads to Mastra AI using the Composio tool router. By the end, you'll have a working Google Ads agent that can create a new customer list for holiday campaigns, get campaign details by campaign id, list all current customer lists in your account through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Google Ads account through Composio's Google Ads MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Google Ads with

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Google Ads tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Google Ads tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Google Ads agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Google Ads MCP server, and what's possible with it?

The Google Ads MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Ads account. It provides structured and secure access to your advertising data, so your agent can perform actions like creating customer lists, retrieving campaign details, and managing audience segments on your behalf.

  • Automated customer list creation: Instantly have your agent create new customer lists for targeted marketing campaigns, streamlining your segmentation workflows.
  • Campaign insights by ID or name: Let your agent fetch detailed information for any ad campaign using its ID or name, making reporting and optimization a breeze.
  • Customer list management: Ask your agent to retrieve and review all your existing customer lists, so you always know who you're targeting.
  • Add or remove contacts from lists: Seamlessly update audience membership by having your agent add or remove contacts from specified customer lists for more dynamic targeting.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Google Ads through MCP.
3

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models
5

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session
6

Create a Tool Router session for Google Ads

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["googleads"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Google Ads MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "googleads" for Google Ads access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
7

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Google Ads toolkit
8

Create the Mastra agent

typescript
const agent = new Agent({
    name: "googleads-mastra-agent",
    instructions: "You are an AI agent with Google Ads tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM
9

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        googleads: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Google Ads toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Google Ads and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["googleads"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      googleads: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "googleads-mastra-agent",
    instructions: "You are an AI agent with Google Ads tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { googleads: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Google Ads through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows
TOOLS

Supported Tools

Every Google Ads action and event your agent gets out of the box.

Add or remove to customer list

Adds or removes contacts from a Google Ads customer list (UserList/audience/remarketing list), not a Google Ads customer account.

Batch Mutate Google Ads Resources

Create, update, remove, or act on supported Google Ads resource types in one request.

Create Callout Asset

Create an immutable account asset containing a validated callout.

Create customer list

Creates a Google Ads customer list (UserList/audience/remarketing list), not a Google Ads customer account.

Get Campaign By Id

GetCampaignById Tool returns details of a campaign in Google Ads.

Get campaign by name

Queries Google Ads via SQL to retrieve a campaign by its exact name.

Get Conversion Action Tag Snippets

Retrieve provider-generated website or call conversion tag snippets after creating a conversion action.

Get conversion ingestion status

Retrieve one Data Manager ingestion status snapshot.

Get customer lists

GetCustomerLists Tool lists all customer lists (audience/remarketing lists) in Google Ads.

Get Required Google Ads Report

Run a prominent, bounded Google Ads report template for Customer, Campaign, Ad, Keyword, Search Term, Dynamic Search Ads Search Term, or Bidding Strategy.

Ingest conversion events

Validate or submit a bounded Google Ads conversion-event batch.

List Accessible Customers

List Google Ads customer resource names directly accessible to the authenticated OAuth user.

List data manager conversion actions

List conversion actions usable as Google Ads Data Manager destinations.

List Sub Accounts

List direct child/sub-accounts under a Google Ads manager (MCC) account.

Mutate Ad Group Ads

Create, update, or remove ads in Google Ads ad groups, including responsive search ads.

Mutate Ad Group Assets

Create, update, or remove links between assets and ad groups.

Mutate Ad Group Bid Modifiers

Create, update, or remove ad group bid modifiers, such as device bid adjustments or hotel-specific bid modifier criteria.

Mutate Ad Group Criteria

Create, update, or remove criteria attached to a Google Ads ad group in a single batch request.

Mutate Ad Groups

Create, update, or remove ad groups within Google Ads campaigns.

Mutate Assets

Create or update supported Google Ads assets such as sitelinks, structured snippets, text assets, lead forms, promotions, calls, price assets, and media assets.

Mutate Asset Sets

Create, update, or remove Google Ads asset sets, which group assets for feeds, locations, and other campaign uses.

Mutate Bidding Strategies

Create, update, or remove portfolio bidding strategies such as Target CPA, Target ROAS, Target Spend, Maximize Conversions, Maximize Conversion Value, and Target Impression Share.

Mutate Campaign Assets

Create, update, or remove links between assets and campaigns.

Mutate Campaign Budgets

Create, update, or remove Google Ads campaign budgets.

Mutate Campaign Criteria

Create, update, or remove campaign-level targeting criteria such as locations, languages, campaign-level negative keywords, devices, schedules, audiences, and IP exclusions.

Mutate Campaign Labels

Create or remove relationships between campaigns and labels.

Mutate Campaigns

Create, update, or remove Google Ads campaigns in batch.

Mutate Campaigns V2

Create, update, or remove Google Ads campaigns in batch.

Mutate Conversion Actions

Create, update, or remove Google Ads conversion actions for conversion tracking configuration.

Mutate Custom Audiences

Create, update, or remove Google Ads custom audiences used to reach users by interests, searches, visited URLs, place categories, or installed apps.

Mutate Customer Assets

Create or remove customer-level asset associations.

Mutate Labels

Create, update, or remove Google Ads labels.

Mutate Portfolio Bidding Strategies

Create, edit, or remove typed Target CPA and Target ROAS portfolio strategies.

Mutate Shared Sets

Create, update, or remove Google Ads shared sets used to group shared criteria, such as negative keyword lists, for reuse across campaigns.

Search Google Ads Fields

Search the Google Ads v23 field metadata catalog with GAQL.

Search Stream GAQL

Execute a Google Ads Query Language (GAQL) query and aggregate every streamed response batch in order.

FAQ

Frequently asked questions

With a standalone Google Ads MCP server, the agents and LLMs can only access a fixed set of Google Ads tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Ads and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Ads tools.

Yes, absolutely. You can configure which Google Ads scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Ads data and credentials are handled as safely as possible.

Start with Google Ads.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Ads tool your agent needs.Free to start.

Start building