How to integrate Google Ads MCP with Kimi Code

Connect Kimi Code 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

How to integrate Google Ads MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Google Ads account to Kimi Code via Composio Connect, so it can create a new customer list for holiday campaigns, get campaign details by campaign ID, list all current customer lists in your account, and more without ever putting your account credentials at risk.

Also integrate Google Ads with

Why use Composio?

Composio provides:

  • Access to 1,500+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Google Ads to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Google Ads account

Back in a Kimi Code session, ask the agent to connect to Google Ads or give it any Google Ads-related task.

For example, ask it to:

  • "Create a new customer list for holiday campaigns"
  • "Get campaign details by campaign ID"
  • "List all current customer lists in your account"

It will prompt you to authenticate and authorize access to Google Ads.

That is it. Composio tools are now available in Kimi Code, and your Google Ads account is ready to use.

Conclusion

You have successfully connected Google Ads to Kimi Code using Composio Connect. Your agent can now manage Google Ads from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,500+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into 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. Kimi Code 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