SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Google Ads MCP with LlamaIndex

Connect LlamaIndex 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.

Get started for freeGet a demo
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.

78 Tools

Introduction

This guide walks you through connecting Google Ads to LlamaIndex using the Composio tool router. By the end, you'll have a working Google Ads agent that can create and update campaigns and ads, research keyword ideas, run GAQL reports, upload conversions, and manage customer lists through natural language commands.

This guide will help you understand how to give your LlamaIndex 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

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKGrok BotCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Google Ads
  • Connect LlamaIndex to the Google Ads MCP server
  • Build a Google Ads-powered agent using LlamaIndex
  • Interact with Google Ads through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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 step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Google Ads account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Google Ads

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Google Ads access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called google ads_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["googleads"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Google Ads actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, google ads)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Google Ads tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Google Ads
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Google Ads tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Google Ads
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Google Ads, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["googleads"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Google Ads actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Google Ads to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Google Ads tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Add or remove to customer list

Submit email contacts for addition to or removal from a Google Ads Customer Match list through an asynchronous offline user data job, marking ad user data and personalization consent as granted.

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 Client

Create a new Google Ads client under an eligible direct parent manager.

Create customer list

Creates a Google Ads Customer Match user list for contact information, not a customer account.

Create data manager user list

Create a Data Manager user list, or validate without creating one.

Create Experiment

Create the experiment definition that begins an experiment setup workflow.

Create Experiment Arms

Create two Google Ads experiment arms in one atomic batch: one control and one treatment arm belonging to the same experiment.

Delete data manager user list

Delete a Data Manager user list, optionally validating only.

End Experiment

Immediately stop a running experiment without deleting its campaigns, or validate that operation.

Generate Keyword Forecast Metrics

Forecast clicks, conversions and costs for a hypothetical keyword campaign without creating resources.

Generate Keyword Historical Metrics

Retrieve historical search volumes, competition, and bid metrics for supplied keywords without creating or changing advertising resources.

Generate Keyword Ideas

Generate keyword ideas and planning metrics from exactly one seed form.

Get Campaign By Id

Retrieve a Google Ads campaign's name and status by numeric campaign ID for the specified or connected customer account.

Get campaign by name

Retrieve the first Google Ads campaign matching an exact name for the specified or connected customer account.

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

List a page of Google Ads customer lists (audience and remarketing user segments), not Google Ads accounts.

Get data manager user list

Get one Data Manager user list without modifying it.

Get Experiment

Get one Google Ads experiment by resource name or numeric ID.

Get Experiment Arm

Get one Google Ads experiment arm, including draft campaigns.

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 ad events

Upload ad events for an allowlisted Data Partner to Google Analytics, not Ads.

Ingest audience members

Validate or asynchronously ingest Data Manager audience members.

Ingest conversion events

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

Ingest users

Ingest account-level identity linkage, not audience-list membership.

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 data manager user lists

List one page of Data Manager user lists and their lifecycle configuration.

List Experiment Arms

List Google Ads experiment arms, including draft campaigns.

List Experiments

List Google Ads experiments, optionally filtered by status and type.

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 Google Ads ad group criteria in a batch, including keywords, audiences, demographics, mobile apps, YouTube placements, topics, webpages, and Shopping listing groups.

Mutate Ad Groups

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

Mutate Ads

Update existing Google Ads ad creative fields.

Mutate Asset Group Assets

Create, update, or remove links between assets and Performance Max asset groups.

Mutate Asset Groups

Create, update, or remove Google Ads asset groups for Performance Max 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 Audiences

Create or update Google Ads audiences combining segment attributes.

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 a batch; removal is irreversible and validate-only can check changes before applying them.

Mutate Campaigns V2

Create, update, or remove Search and Display Google Ads campaigns in a batch; new campaigns default to paused when status is omitted.

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

Update one Google Ads customer's mutable account settings using CustomerService.

Mutate Customer Assets

Create or remove customer-level asset associations.

Mutate Keyword Plan Ad Group Keywords

Create, update, or remove Google Ads Keyword Planner ad group keywords.

Mutate Keyword Plan Ad Groups

Create, update, or remove Google Ads Keyword Planner ad groups.

Mutate Keyword Plan Campaign Keywords

Create, update, or remove negative keywords in Keyword Plan campaigns.

Mutate Keyword Plan Campaigns

Create, update, or remove campaigns in an existing Keyword Plan.

Mutate Keyword Plans

Create, update, or remove saved Google Ads Keyword Planner plans.

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 Criteria

Create or remove criteria in a Google Ads shared set, such as negative keywords or excluded placements shared across campaigns.

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.

Mutate User Lists

Create, update, or remove general Google Ads user-list resources used for audience targeting and remarketing.

Remove all audience members

Validate or asynchronously remove all members of Data Manager audiences.

Remove audience members

Remove specific users from Data Manager audience destinations.

Remove users

Remove users identified by hashed user data from Data Manager destinations.

Schedule Experiment

Schedule a Google Ads experiment and return its long-running operation.

Search GAQL

Run one page of a GAQL search and return its continuation token.

Search Google Ads Fields

Search the Google Ads v26 field metadata catalog with GAQL.

Search Stream GAQL

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

Update data manager user list

Update mutable Data Manager user-list metadata, optionally validating only.

Update Experiment

Update mutable fields on one Google Ads experiment.

Update Experiment Arms

Update one or more Google Ads experiment arms.

Upload Call Conversions

Upload offline call conversions to Google Ads, or validate them without uploading using validate_only.

Upload Click Conversions

Upload offline click conversions with optional enhanced-conversion identifiers, consent, and cart data.

Upload Conversion Adjustments

Upload retractions, restatements, or enhancements of existing conversions.

Upload User Data

Append or remove already-hashed user data in a Google Ads Customer Match list.

FRAMEWORKS

How to build Google Ads MCP Agent with another framework

Claude Code logo

Claude Code

Use Google Ads MCP with Claude Code

Cursor logo

Cursor

Use Google Ads MCP with Cursor

ChatGPT logo

ChatGPT

Use Google Ads MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Google Ads MCP with Claude Cowork

Antigravity logo

Antigravity

Use Google Ads MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google Ads MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Google Ads MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Google Ads MCP with Grok Bot

Codex logo

Codex

Use Google Ads MCP with Codex

Kimi Code logo

Kimi Code

Use Google Ads MCP with Kimi Code

Grok Build logo

Grok Build

Use Google Ads MCP with Grok Build

VS Code logo

VS Code

Use Google Ads MCP with VS Code

OpenCode logo

OpenCode

Use Google Ads MCP with OpenCode

OpenClaw logo

OpenClaw

Use Google Ads MCP with OpenClaw

Hermes logo

Hermes

Use Google Ads MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Google Ads MCP with Atomic Agent

CLI logo

CLI

Use Google Ads MCP with CLI

Google ADK logo

Google ADK

Use Google Ads MCP with Google ADK

LangChain logo

LangChain

Use Google Ads MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google Ads MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google Ads MCP with Mastra AI

CrewAI logo

CrewAI

Use Google Ads MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Google Ads MCP with Pydantic AI

AutoGen logo

AutoGen

Use Google Ads MCP with AutoGen

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. LlamaIndex 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