By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Le Chat to Google Ads is the Ryze AI connector. Connect Google Ads in a Ryze AI workspace with your Google sign-in. Then, in Mistral Vibe (the name Le Chat has carried since May 2026), open Connectors, click + Add Connector, choose the Custom MCP Connector tab, enter a name such as RyzeAI with the server URL https://connector.get-ryze.ai/mcp, click Connect and finish the Ryze AI sign-in.
- In Ryze AI open Integrations, find Google Ads and click Connect
- Sign in to Google with the login that reaches your ad accounts and keep every permission checked
- In Mistral Vibe open Connectors, + Add Connector, Custom MCP Connector, then enter the name and URL
- Click Connect, finish the Ryze AI sign-in, choose workspaces and click Allow connection
Le Chat to Google Ads at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: one hosted MCP address that a Mistral administrator adds in Vibe Work as a Custom MCP Connector |
| Server address | https://connector.get-ryze.ai/mcp |
| Where it goes in Le Chat | chat.mistral.ai, Connectors in the sidebar, + Add Connector, then the Custom MCP Connector tab |
| Sign-in | Mistral detects the method from the address. Ryze AI answers with OAuth 2.1 and dynamic client registration, so nobody types a client ID or secret |
| Google Ads tools | 16: 8 read, 7 write and 1 delete |
| Can it change the account | Yes, when the connected Google user is Standard or Admin in Google Ads. Work asks for approval before an action that creates, modifies or deletes, unless that function is on Always allow |
| Mistral plan needed | None named in Mistral's connector docs. The pricing page checks Custom MCP connectors (beta) on Free, Pro, Team and Enterprise. Adding one takes an administrator |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. Adding the connector is free |
| Google's own server | google-ads-mcp 0.0.6, open source, run on your computer or your own cloud. Its guide does not name Le Chat or Mistral |
| Google Ads permission | One OAuth scope, adwords, for reading and writing alike. The user's role in each Google Ads account decides what goes through |
| Last tested | Connector checked November 13, 2026. No step was run inside Mistral Vibe |
Before you start
- Administrator rights in Mistral. Mistral's docs call adding a custom MCP connector an administrator-only feature, and on Free, Pro and Student plans the account owner holds that role by default. The docs name no minimum plan, and the pricing page marks Custom MCP connectors, labeled beta, on Free, Pro, Team and Enterprise. On a team or organization account, ask an administrator to add it.
- A Google login with access to at least one Google Ads account. You pick it on the Ryze AI Connect step. Edits through the tools require standard or admin access in Google Ads, and a read-only login still allows reading. Agencies connect their manager (MCC) login one time.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and annual billing takes 30% off the first year. Connecting the connector is free; the Google Ads tools need an active plan or trial.
- A server reachable over HTTPS. Mistral requires a valid TLS certificate. The Ryze AI connector URL meets that, so you add it exactly as written.
How to connect Le Chat to Google Ads
Setup has two parts: Google Ads is connected inside Ryze AI, then Mistral Vibe is pointed at the Ryze AI connector. The Mistral steps follow its MCP connector docs. Ryze AI has no help-center page for Mistral and the sign-in was not tested inside Mistral Vibe while this page was written, so use the troubleshooting list below if a step differs on your screen.
Connect Google Ads in Ryze AI
Log in to Ryze AI or create an account. In the left sidebar choose Integrations, look under Advertising for Google Ads and click Connect.
Pick your Google login and approve every permission
Select the Google login that holds your ad accounts and keep every requested permission ticked. The Ryze AI card turns to Connected. You pick no account here, since all accounts that login reaches are visible to Ryze AI.
Open Connectors in Mistral Vibe
Go to chat.mistral.ai (the address is unchanged since Le Chat became Mistral Vibe), open the Connectors page from the sidebar and click + Add Connector. Switch to the Custom MCP Connector tab.
Enter the connector name and URL
Connector name: a unique identifier with no spaces or special characters, for example RyzeAI. Server URL: https://connector.get-ryze.ai/mcp. The description is optional.
Click Connect
Mistral detects the authentication method on its own. Ryze AI uses OAuth 2.1 with dynamic client registration, so you enter no client ID or secret.
Finish the Ryze AI sign-in
Complete the Ryze AI sign-in when Mistral prompts, choose the workspaces that hold your Google Ads connection and click Allow connection. Then start a new chat and ask a Google Ads question.
Sources: Mistral docs: MCP connectors, Mistral docs: Connectors, Mistral help: Le Chat is now Vibe. Checked November 15, 2026. The Ryze AI Google Ads guide covers the Google sign-in on the Ryze AI side.
Approvals and Always allow
Mistral lets you decide how much each function may do without asking. To pre-authorize only the reads you trust:
- Open Connectors, then the My Connectors tab.
- Open the Ryze AI card and go to its Functions tab.
- Switch Always allow on for read functions you want to run without a prompt each time.
- Leave Always allow off for the write and delete functions so Mistral asks before each one.
- Use Refresh tools on the same tab to reload the function list, which Mistral calls useful after a connector update.
Mistral's Safety and approvals page says Work pauses before anything that creates, modifies, sends, posts or deletes, and offers three answers: Continue for that one action, Always allow for the function until the session ends, or Decline. The toggles on the Functions tab belong to each user, so your choices leave a teammate's settings alone. Mistral advises keeping write functions on manual approval until you trust the connector.
Sources: Mistral docs: MCP connectors, Mistral docs: Safety and approvals. Checked November 15, 2026.
Vibe Work and Vibe Code
Mistral Vibe Work and the old Le Chat address
Mistral's changelog and launch post date the switch from Le Chat to Vibe to May 28, 2026, with the same chat.mistral.ai address and the same login. Since September 22, 2026 the old Chat tab and Work run as one experience, and the Connectors page sits in Work. Mistral's old docs link for MCP connectors redirects to the Vibe docs, so a tutorial that still says Le Chat shows this same screen.
Vibe Code (CLI and VS Code extension)
Vibe Code, the coding side of Vibe, keeps MCP servers in ~/.vibe/config.toml or a project's .vibe/config.toml and adds them with vibe mcp add. Mistral's docs say a remote server added by URL opens the browser to sign in, with a client registered dynamically when no client ID is set, and that Vibe Code can also start a local server from a command, which Work cannot. Ryze AI has not reviewed the Vibe Code setup, so this guide gives steps for Vibe Work only.
Vibe Work and MCP: the facts in one table
| Topic | What Mistral's pages say |
|---|---|
| Product name | Vibe. Work, on the web and in the iOS and Android apps, is the old Le Chat. Mistral does not say whether a custom connector can be added or used from the apps |
| Where a server is added | The Connectors page from the sidebar, + Add Connector, Custom MCP Connector tab |
| Plan | Mistral's pricing page shows a check mark for the beta Custom MCP connectors feature under Free, Pro, Team and Enterprise. The connector docs name no minimum plan |
| Who can add one | An administrator, which on Free, Pro and Student is the account owner by default |
| Transport | A remote address over HTTPS with a valid TLS certificate. Mistral calls Streamable HTTP the current standard and shows no field for a local command |
| Sign-in | Detected from the URL: none, a Bearer token or Basic Auth in the Authorization header, or OAuth 2.1 with dynamic client registration |
| Approval | A prompt before actions that create, modify, send, post or delete: Continue, Always allow for the session, or Decline |
| Picking the connector | Work calls a connected connector when it fits the request. The + icon or / in the chat box, then Tools, picks one for a task |
| Not supported yet | Dynamic tool discovery, resources and automatic prompt templates |
| Where it is managed | Users: Connectors, My Connectors tab. Admins: Admin Panel, Administration, Connectors, set to Allowed, Restricted or Blocked per workspace |
Sources: Mistral docs: Vibe, MCP connectors, Safety and approvals, Admin Panel connectors, Vibe Code MCP servers, Mistral pricing. Checked November 15, 2026.
Google Ads access and scopes
Three separate gates sit between Mistral Vibe and your ads. Google controls the Google side; Ryze AI sets no Google Ads permissions of its own.
- Google login
- You pick it at the Connect click on the Ryze AI Google Ads card. Every Google Ads account that login opens becomes visible to Ryze AI, including client accounts below a manager (MCC) login. Anything outside the login stays hidden.
- Access level in Google Ads
- Standard or admin access is needed before changes go through. A Google user with read-only access can view data but not edit it, so a read-only login is the firm way to rule out edits.
- Mistral administrator and function settings
- Only a Mistral administrator can add the connector. After that, each user sets Always allow per function on the Functions tab of the connector card, and Mistral advises manual approval for write functions. Organization admins can also turn MCP Connectors off for a whole workspace.
The four Google permissions
On the Google consent screen Ryze AI asks for four permissions: the Google Ads scope https://www.googleapis.com/auth/adwords together with openid, email and profile. Keep all of them checked, or the connection does not complete. The right column is Google's own wording for each.
| Scope | Google's description |
|---|---|
| https://www.googleapis.com/auth/adwords | See, edit, create, and delete your Google Ads accounts and data. |
| openid | Associate you with your personal info on Google |
| See your primary Google Account email address | |
| profile | See your personal info, including any personal info you've made publicly available |
What each Google Ads role allows in Le Chat
Because one scope covers both reading and editing, the scope list says nothing about what Le Chat may change. Google's access model page leaves that to the role the connected user holds inside each Google Ads account.
| Role in Google Ads | What Google's role table allows | What Le Chat gets through Ryze AI |
|---|---|---|
| Read-only | View campaigns, use planning tools, run campaign performance reports, view users, managers and product links, view billing | The 8 read tools. Write and delete calls fail |
| Standard | Everything Read-only allows, plus editing campaigns | All 16 tools |
| Admin | Everything Standard allows, plus adding or removing product links and managing who has access | All 16 tools, as with Standard |
Some things stay out of reach at any role: accounts the login cannot open, clients under a manager login you never connected, video file uploads (a video ad takes a YouTube link), taking people off a Customer Match list, and bringing back a removed item, since Google Ads has no undo. For a client reached through a manager, Google wants the manager's ID as login-customer-id, and Google's own account list shows only accounts the user reaches directly.
Sources: Google OAuth 2.0 scopes, Google Ads API access model, Google Ads access levels, Google Ads API OAuth overview. Checked November 14, 2026.
Removing access
You can cut access in three places: View on the Google Ads card in Ryze AI to disconnect the login, the Connectors page in Mistral Vibe to remove the Ryze AI connector, or your Google Account permissions page to revoke third-party access.
What Le Chat can do in Google Ads
The Ryze AI connector offers Mistral Vibe 16 Google Ads tools, which Mistral calls functions: 8 read, 7 write and 1 delete. Each call runs as the Google login you connected, so Google's own access rules apply.
| Tool | Type | What it does |
|---|---|---|
| google_ads__getAccountSummary | Read | Aggregate account metrics for a date range. |
| google_ads__getAccountHierarchy | Read | The manager and sub-account tree of an account. |
| google_ads__listAccessibleCustomers | Read | Every customer account the connected login can open. |
| google_ads__listConversionActions | Read | The conversion actions defined in an account. |
| google_ads__listRecommendations | Read | Google's optimization recommendations for an account. |
| google_ads__runRawGaql | Read | A GAQL query that you write, including change history from change_event. |
| google_ads__generateKeywordIdeas | Read | Keyword Planner ideas from seed keywords, a URL or both. |
| google_ads__generateKeywordHistoricalMetrics | Read | Average monthly searches, competition and top-of-page bid range for a keyword list you supply. |
| google_ads__runRawMutate | Write | Create or update campaigns, budgets, ad groups, ads, keywords, criteria and assets. |
| google_ads__runRawCustomAudienceMutate | Write | Create or update custom audiences based on keywords, URLs, place categories or apps. |
| google_ads__runRawUserListMutate | Write | Create or update user lists, including Customer Match lists. |
| google_ads__uploadCustomerMatchMembers | Write | Add people to a Customer Match list; every identifier is normalized and SHA-256 hashed on the server before it reaches Google. |
| google_ads__uploadImageAsset | Write | Upload an image from a URL as an image asset. |
| google_ads__applyRecommendation | Write | Apply Google recommendations. |
| google_ads__dismissRecommendation | Write | Dismiss Google recommendations. |
| google_ads__runRawMutateDelete | Delete | Permanently remove resources. The tool description tells the agent to use it only on an item-by-item approved list. |
Mistral sorts connector functions into read and write. Work asks before a call that creates, modifies, sends, posts or deletes, and you can switch on Always allow per function under Connectors, My Connectors, the Ryze AI card, Functions tab. Mistral suggests keeping write functions on manual approval, so leave Always allow off for the write and delete tools. Four Ryze AI tools also accept a validateOnly switch for a dry run: google_ads__runRawMutate, google_ads__runRawMutateDelete, google_ads__runRawCustomAudienceMutate and google_ads__runRawUserListMutate. In the Ryze AI chat the Tool approvals setting is separate and starts on Skip all approvals. For a hard read-only guarantee, connect a Google login that only has read access.
Limits in numbers
Google sets most ceilings per Google Cloud project or per customer ID. No test answer showed the API access level of the project behind Ryze AI, so its daily ceiling is not stated here. Mistral's docs give no number for connectors, tools or calls in Work.
| Limit | What applies |
|---|---|
| Daily operations, per Google Cloud project | Explorer access: 2,880 against production accounts. Basic: 15,000. Standard: no daily cap. Google counts a day as a sliding 24-hour window |
| What one operation is | One Search or SearchStream request. Refused requests count; later pages fetched with a page token do not |
| Requests per second | No fixed figure. An overrun returns RESOURCE_TEMPORARILY_EXHAUSTED, and Google suggests retrying after 2, 4, then 8 seconds |
| Rows per report page | Up to 10,000. An unused next_page_token expires after about two hours |
| Change history | The past 30 days only. A change_event query needs a date filter and a LIMIT of 10,000 or less, and a fresh change can take up to 3 minutes to appear |
| Keyword Planner | 1 request per second per customer ID. One history request takes up to 10,000 keywords and 10 locations, and monthly volumes reach back up to 4 years |
| Changes in one request | Up to 10,000 mutate operations |
| How fresh the numbers are | Clicks, impressions and cost refresh hourly; impression share and auction insights usually daily |
| Ryze AI tool inputs | A GAQL query of 1 to 10,000 characters. 1 to 100,000 people per Customer Match upload call. An image asset name of 1 to 128 characters |
| API version | The test answers named v24, which Google's timetable retires in May 2027. The newest version is v26, released October 14, 2026 |
Sources: Google Ads API quotas, API access levels, rate limits, paging, change event, keyword historical metrics, Google Ads data freshness, API sunset dates. Checked November 14, 2026. Ryze AI tool inputs from the tool definitions loaded on November 13, 2026.
Google Ads calls through the connector, tested
On November 13, 2026, nine Google Ads calls went to the live connector from Claude Code, at the address Le Chat would use. Two asked for data and seven carried a mistake on purpose. The Google Ads account behind them is real, so the table names no account, ID or figure.
| What was sent | Tool | Answer from Google Ads |
|---|---|---|
| A list of the accounts the login reaches | google_ads__listAccessibleCustomers | Worked: customer resource names came back |
| Search history for three Google Ads related keywords, in English, for the United States on Google Search | google_ads__generateKeywordHistoricalMetrics | Worked: for each keyword, average monthly searches, competition, a competition index, a top-of-page bid range and 12 monthly values |
| GAQL selecting campaign.daily_budget, a field Google does not have | google_ads__runRawGaql | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| GAQL reading campaign_experiment, a resource that does not exist | google_ads__runRawGaql | Refused, HTTP 400, UNRECOGNIZED_FIELD |
| GAQL that starts with SELEC | google_ads__runRawGaql | Refused, HTTP 400, EXPECTED_SELECT |
| change_event without a LIMIT | google_ads__runRawGaql | Refused, HTTP 400, LIMIT_NOT_SPECIFIED |
| change_event with LIMIT 10001 | google_ads__runRawGaql | Refused, HTTP 400, INVALID_LIMIT_CLAUSE |
| GAQL against an invented 10-digit customer ID | google_ads__runRawGaql | Refused, HTTP 401, CUSTOMER_NOT_FOUND |
| Keyword history with the bare numbers 1000 and 2840 for language and location | google_ads__generateKeywordHistoricalMetrics | Refused, HTTP 400, RESOURCE_NAME_MALFORMED |
No answer carried a quota counter or a rate-limit header, and the error payloads named Google Ads API v24.
First 3 prompts and 10 jobs for Le Chat
Each prompt below says what it asks for and which functions Mistral Vibe would call. The answers depend on your own accounts, so no sample figures appear here.
1. Start with a read of one account
Use the RyzeAI connector to list the Google Ads accounts I can reach, then give me account totals for last month for the one named in my next message.
Tools used: google_ads__listAccessibleCustomers, google_ads__getAccountSummary
What comes back: The accounts your Google login opens, then the aggregate metrics for the account and month you name.
2. Check who changed the account
Use the RyzeAI connector to query change_event with GAQL for the past week, with a LIMIT of 1000, and tell me which changes were made, by whom and when.
Tools used: google_ads__runRawGaql
What comes back: Rows from the change_event resource. Ryze AI's documentation says change history reaches back up to 30 days, and Google refuses a change_event query without a LIMIT.
3. Price a keyword list
Use the RyzeAI connector to pull Keyword Planner ideas for my site URL, then show monthly searches, competition and the top-of-page bid range for the ones I choose.
Tools used: google_ads__generateKeywordIdeas, google_ads__generateKeywordHistoricalMetrics
What comes back: Keyword ideas for the URL, then Keyword Planner history for the keywords you pick.
Begin with reads. When Mistral asks permission for a write function, check the campaign or budget it names before you approve.
10 jobs to hand to Le Chat
Ten jobs to give Le Chat once the connector is in, each with the Ryze AI tool behind it. In the test the account list and the keyword history worked, the change log query went out only in two forms Google refused, and nothing that edits an account was run. Work pauses for your approval on the jobs that change data unless that function is on Always allow.
| Job | Ask Le Chat | Tool | Works on the default connection |
|---|---|---|---|
| Campaign report | Use RyzeAI to show spend, conversions and ROAS per campaign for last month. | google_ads__getAccountSummary, google_ads__runRawGaql | Yes |
| Change log | Use RyzeAI to list who changed what in this account over the last 14 days. | google_ads__runRawGaql (change_event) | Yes, within 30 days and a LIMIT of 10,000 |
| Account map | Use RyzeAI to list every Google Ads account I can reach and the manager each one sits under. | google_ads__listAccessibleCustomers, google_ads__getAccountHierarchy | Yes. The account list worked in the test |
| Keyword ideas | Use RyzeAI to suggest keywords from my landing page URL. | google_ads__generateKeywordIdeas | Yes |
| Keyword pricing | Use RyzeAI to show monthly searches, competition and the top-of-page bid range for these keywords. | google_ads__generateKeywordHistoricalMetrics | Yes. It worked in the test |
| Conversion setup | Use RyzeAI to list the conversion actions in this account. | google_ads__listConversionActions | Yes |
| Recommendations | Use RyzeAI to list Google's recommendations, apply the two I pick and dismiss the rest. | google_ads__listRecommendations, google_ads__applyRecommendation, google_ads__dismissRecommendation | Listing, yes. Applying or dismissing needs a Standard or Admin user |
| Campaign edits | Use RyzeAI to add these negative keywords and lower the daily budget of the campaign I name. | google_ads__runRawMutate | Yes with Standard or Admin access; refused for a Read-only user |
| Image asset | Use RyzeAI to upload the image at this URL and link it to the asset group I name. | google_ads__uploadImageAsset, google_ads__runRawMutate | Yes with Standard or Admin access. No video files |
| Customer Match list | Use RyzeAI to create a Customer Match list and add the customer contacts I list below. | google_ads__runRawUserListMutate, google_ads__uploadCustomerMatchMembers | Yes with Standard or Admin access. Members can be added, not removed |
2 ways to connect Le Chat to Google Ads
A custom connector in Vibe Work has to point at a remote MCP server over HTTPS, and Work cannot start a local command. The Ryze AI connector is the main way: a Google sign-in inside Ryze AI, one address in Vibe Work and nothing to host. The second row is the do-it-yourself route that Mistral's support for any MCP-compatible server leaves open. The other Google Ads options read for this guide on November 14, 2026 follow the table, each with the reason it is left out, and none was tried in Vibe Work.
| Way | Runs where | Setup | What it reaches in Google Ads | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user. The same address works in Claude, ChatGPT and other MCP clients | An administrator adds a Custom MCP Connector named, for example, RyzeAI with https://connector.get-ryze.ai/mcp, clicks Connect and signs in. Mistral detects OAuth 2.1 with dynamic client registration | 16 tools: reports and GAQL, account lists, Keyword Planner, recommendations, changes to campaigns, budgets, keywords, audiences and assets, and one delete tool | Paid Ads is $89 per month with a 7-day free trial; Agency is $279 per month. Adding the connector is free |
| Your own MCP server on the Google Ads API | Code you deploy at a public HTTPS address with a valid TLS certificate | Enable the Google Ads API in a Google Cloud project with Explorer, Basic or Standard access and sign users in with the adwords scope. No developer token is needed since Google retired them on September 9, 2026. Then add the address as a Custom MCP Connector, with a sign-in Work can detect | Whatever your code calls, within your project's daily operations. Explorer access cannot use Keyword Planner or the other planning services | Hosting and upkeep are yours |
Other Google Ads options and why they are not in the table
- Google's google-ads-mcp server. Open source from the Google Ads API team. Version 0.0.6 of November 2, 2026 has 3 read tools and 4 for standalone assets, video uploads and labels behind a propose-and-confirm step, and a tools_config.yaml setting can switch the change tools off. It cannot create, change, pause or enable campaigns, ad groups, ads, budgets or bids, and it has no Keyword Planner tool. You run it as a local process with Application Default Credentials, which Vibe Work cannot start, or on infrastructure of your own such as Cloud Run. That remote mode wants your OAuth client ID and secret typed into the client, and Mistral's docs describe no field for them. Google's guide names ChatGPT, Claude, Claude Code, Codex, Cursor, VS Code, the Gemini command-line tool and Antigravity, not Le Chat or Mistral.
- Google Ads API agent skills and the Developer Assistant. Both serve coding agents. The skills name Antigravity, Claude Code, Codex and Cursor. Developer Assistant 4.0.0 is a plugin for Antigravity and Claude Code that writes any change out as code and never runs it.
- Composio. A hosted server with 78 Google Ads tools behind Composio's managed OAuth. Its page names Claude, Claude Code, ChatGPT, Cursor, Codex, VS Code, Antigravity, Grok Bot and others, not Le Chat.
- Zapier MCP. A hosted list of Google Ads actions, from Create Report and Set Campaign Status to a raw API Request, at 2 Zapier tasks per successful call. Zapier names Claude, Claude Code, ChatGPT, Cursor and Codex as popular clients, lists 32 more, and says any client that supports Streamable HTTP works. This guide did not record whether Le Chat is on that list.
- Windsor.ai and Coupler.io. Hosted connectors that bring Google Ads data into an AI chat. Windsor.ai's page names Claude, ChatGPT, Copilot, Perplexity, Gemini and Cursor "or more", and its ChatGPT and Claude guides describe write-back, such as pausing campaigns or adjusting budgets from ChatGPT. Coupler.io names Claude, ChatGPT, Gemini, Perplexity, Cursor, Copilot and OpenClaw and answers read-only from data it syncs on a schedule. Its Custom MCP option hands out a server URL and a Bearer token, a sign-in type Work detects, but Mistral's page does not say where such a token is typed.
- cohnen/mcp-google-ads, open source. 5 reporting tools in a local Python process, documented for Claude Desktop and Cursor. Vibe Work cannot start a local process.
- Mistral's connector directory. Vibe Work also offers Featured Connectors and an MCP Connectors directory for administrators. This guide did not check whether either holds a Google Ads connector.
Which one to pick
Ryze AI is the best way to connect Le Chat to Google Ads for reports, keyword research and campaign changes from one Vibe Work chat, with two caveats: the tools need an active Ryze AI plan or trial, and changes go through only for a Standard or Admin Google user. Build your own server when you want code you control and can get Google Ads API access for a Cloud project. Pick Google's google-ads-mcp for GAQL reports and asset or label work in an assistant its guide names, such as Claude or ChatGPT. The other options are written for other assistants or coding agents, or were not tried in Vibe Work.
Sources: Google Ads MCP server guide, googleads/google-ads-mcp, Google Ads API agent skills, Google Ads API Developer Assistant, developer token sunset, Composio Google Ads, Zapier MCP for Google Ads, Windsor MCP, Windsor.ai ChatGPT guide, Coupler.io Google Ads MCP, cohnen/mcp-google-ads. Checked November 14, 2026. Mistral docs: MCP connectors. Checked November 15, 2026.
Le Chat, Google Ads and MCP: dates that matter
| Date | What happened |
|---|---|
| September 2, 2025 | Le Chat gained custom MCP connectors and a directory of more than 20 connectors (beta), open to every user, Free plan included. |
| October 7, 2025 | Google announced the open-source Google Ads API MCP Server. The first release was read-only. |
| May 22, 2026 | Work mode reached Le Chat as a Preview, with connectors on by default. |
| May 28, 2026 | Le Chat became Vibe at chat.mistral.ai, and Mistral's docs moved from /le-chat to /vibe. |
| June 24, 2026 | Mistral added per-workspace and per-tool connector controls for admins, connectors that hold several logins, and the Connectors Debugger. |
| September 9, 2026 | Google retired Google Ads API developer tokens. API access levels now belong to the Google Cloud project. |
| September 22, 2026 | Chat and Work merged into one Vibe experience. Enterprise organizations move from October 1, 2026, within about six months. |
| October 14, 2026 | Google released Google Ads API v26, the newest major version. |
| November 2, 2026 | google-ads-mcp 0.0.6 added asset and label tools with propose-and-confirm, the first release with tools that change an account. |
| February 2027 | Google Ads API v23, the oldest version still served in November 2026, reaches its sunset. |
Sources: Mistral changelog, Mistral release notes, Mistral news, September 2, 2025, Mistral news, May 22, 2026, Mistral news, May 28, 2026, Mistral news, June 24, 2026. Checked November 15, 2026. Google Ads Developer Blog, October 7, 2025, google-ads-mcp releases, developer token sunset, Google Ads API sunset dates. Checked November 14, 2026.
How this guide was tested
Three things stand behind this guide: a check of the live connector on November 13, 2026, with the Google Ads calls sent from Claude Code; Google's pages as read on November 14, 2026; and Mistral's pages as read on November 15, 2026.
| What was run | What came back |
|---|---|
| The connector address with no sign-in | HTTP 401 with a WWW-Authenticate header that points to the sign-in details, the answer Mistral's docs expect from an OAuth server. |
| The connector's sign-in details | Both discovery files loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and the scopes mcp:read and mcp:write. |
| The Google Ads tool list, signed in | 16 tools, 8 read, 7 write and 1 delete, under the names in the tools table. All 16 take an optional connection_id, and 15 also take customerId and loginCustomerId. |
| Two reads meant to return data | The account list and the keyword history both worked. No value from them is shown, because the account is real. |
| Seven calls with a deliberate mistake | All seven were refused. The messages are in the errors table below. |
| One Search Console call | It listed the Google Ads connector questions people search for, used to pick FAQ questions. No figure from it is printed. |
Not run for this guide: any step inside Mistral Vibe. No Mistral account was used, so the Connectors form, the sign-in prompt, the Functions tab and the approval prompt follow Mistral's documentation as read on November 15, 2026. The calls came from Claude Code, which reaches the same address and the same 16 tools. Reads of account data (account summary, hierarchy, conversion actions, recommendations, keyword ideas and any GAQL query that returns rows) were skipped because the account is real, and the 7 write tools and the delete tool were not run because they change it. No rate limit or daily quota was reached. Google's server and the third-party options were not tried.
Le Chat and Google Ads errors and fixes
Exact error messages from the test
Google Ads sent these messages back in the test on November 13, 2026. Each HTTP 400 answer also carried the outer line "Request contains an invalid argument." If one shows up inside a Le Chat tool call, here is the cause and what to ask next.
| Message | What it means | What to ask Le Chat |
|---|---|---|
| Unrecognized field in the query: 'campaign.daily_budget'. | That field does not exist on the resource. The Ryze AI tool description names campaign_budget.amount_micros, selected from campaign. | Ask it to check the field name and run the query again. |
| Unrecognized field in the query: 'campaign_experiment.name'. | Google reports a resource that does not exist as an unknown field. Experiments sit in the experiment resource. | Ask for the same question through the experiment resource. |
| Error in query: expected SELECT instead of SELEC. | The GAQL text is malformed. | Ask Le Chat to rewrite the query and send it again. |
| Change event requests must specify a LIMIT in query and LIMIT should be less than or equal to 10k. | A change history query arrived with no LIMIT. | Ask for the query again with LIMIT 10000 or lower. |
| Change event requests must specify a LIMIT less than or equal to 10k. | The query asked for more than 10,000 change rows. | Lower the LIMIT, or split the date range and continue from the last timestamp. |
| No customer found for the provided customer id. | The customer ID does not exist. The wrapping message talks about a missing credential, yet the same connection had answered other calls seconds earlier. | Ask Le Chat to list your accounts with google_ads__listAccessibleCustomers and use an ID from that list. |
| Resource name '1000' is malformed: expected 'languageConstants/{criterion_id}'. | Keyword Planner wants full names such as languageConstants/1000 and geoTargetConstants/2840 in place of bare numbers. | Ask Le Chat to resend the request with full resource names. |
Other problems
- Add Connector is missing or refused
- Mistral says adding a custom MCP connector is administrator-only. On Free, Pro and Student plans the account owner is the administrator. On a shared account, ask an administrator to add it. An organization admin may also have switched MCP Connectors off for your workspace.
- Mistral shows "MCP connection requires additional information or is invalid"
- Mistral prints this when the setup check fails. Confirm the address ends in /mcp exactly as given. Mistral's checklist also covers HTTPS, the initialize handshake and the 401 answer an OAuth server owes, which the connector gave in the test.
- The connector name is rejected
- Mistral wants a unique name with no spaces or special characters. Use RyzeAI.
- The Google Ads tools do not load
- Open a fresh chat, then click Refresh tools on the Functions tab of the Ryze AI card. Still nothing: check that the Google Ads card in Ryze AI reads Connected, then remove the connector and add it back. Mistral lists dynamic tool discovery as unsupported for custom connectors; how that affects a platform connected in Ryze AI later was not verified.
- The sign-in does not complete
- Finish the Ryze AI sign-in, choose workspaces and click Allow connection. If the window closed early, click Connect on the connector card again.
- Mistral asks before a function runs
- Work asks before anything that creates, modifies, sends, posts or deletes, and Mistral's pages do not say whether a custom connector's read functions ask by default. Pick Always allow in the prompt to skip the question for that function until the session ends, or turn on the Always allow toggle on the Functions tab, for read functions only.
- An account is missing from the results
- Ryze AI sees what the connected Google login can open and nothing else. For client accounts connect the manager (MCC) login, or add a second login with Add one more account. Client accounts under a manager also need loginCustomerId on MCP calls.
- A change is refused
- The connected Google user may hold read access only. Raise it inside Google Ads, because Ryze AI does not manage those permissions.
- Recent conversions look low
- That is Google's own reporting lag, which Ryze AI cannot shorten. Conversions under attribution models other than last click arrive later still.
- Mistral says a subscription is required
- The functions need an active Ryze AI plan or free trial. Start the trial and ask again.
Source for the Mistral message: Mistral docs: MCP connectors. Checked November 15, 2026.
Terms on this page
- MCP
- The Model Context Protocol, an open standard through which AI models reach outside data and apps. Mistral calls an MCP server added by its address a Custom MCP Connector.
- Function
- What Mistral's MCP Connectors page calls one action a connector offers. Mistral's Safety and approvals page and the rest of this page call it a tool.
- GAQL
- Google Ads Query Language. A query picks fields from one resource and returns rows of attributes, segments and metrics.
- Customer ID and login-customer-id
- The customer ID is the 10-digit number of a Google Ads account, sent without hyphens. login-customer-id carries the manager account's ID when access to a client runs through that manager.
- Manager account (MCC)
- A Google Ads account for viewing and managing many Google Ads accounts, other managers included, from one place.
- Access level
- Two meanings. Inside an account, a user is Email-only, Billing, Read-only, Standard or Admin. In the API, a Google Cloud project holds Test, Explorer, Basic or Standard access, which sets its daily operations.
- Change event
- The API resource behind change history: what changed, the old and new values, who made the change and from which client, over the past 30 days.
Sources: Google Ads MCP server guide, GAQL overview, API call structure, manager accounts, change_event reference. Checked November 14, 2026. Mistral docs: MCP connectors. Checked November 15, 2026.
Frequently asked questions
How do I connect Le Chat to Google Ads?
Connect Google Ads in a Ryze AI workspace: open Integrations, click Connect on Google Ads and approve every permission. Then in Mistral Vibe (formerly Le Chat) open Connectors, + Add Connector, the Custom MCP Connector tab, enter the name RyzeAI and the URL https://connector.get-ryze.ai/mcp, and click Connect.
Is Le Chat the same as Mistral Vibe?
Yes. Mistral's changelog dates the change from Le Chat to Vibe to May 28, 2026, and the address is still chat.mistral.ai. Connectors are in Vibe Work. This guide uses both names so older searches still land here.
Is there a Le Chat Google Ads MCP connector?
Mistral lets an administrator add a custom MCP connector by server URL, and the Ryze AI connector is one you can add that way. Mistral also keeps a directory of connectors; this page did not verify one for Google Ads.
Does Google have an official Google Ads MCP server?
Yes. The Google Ads API team publishes google-ads-mcp, an open-source server whose version 0.0.6 of November 2, 2026 has 3 read tools and 4 for assets, video uploads and labels. You run it yourself on your computer or on infrastructure of your own such as Cloud Run, and Google's guide does not name Le Chat or Mistral Vibe.
What is the Google Ads MCP server URL for Le Chat?
For the Ryze AI connector it is https://connector.get-ryze.ai/mcp, the same for every user, typed into the Server URL field of a Custom MCP Connector. Google's guide describes no hosted address for its own server: you run it locally or deploy it yourself.
Which Google Ads connector should I use with Le Chat?
Ryze AI is the best Google Ads connector for Le Chat when you want reads, Keyword Planner research and changes in one chat, but it needs a Ryze AI plan or trial. Google's own google-ads-mcp is self-hosted, its guide does not name Le Chat or Mistral, and its remote mode expects the client to hold your OAuth client ID and secret.
Which Mistral plan do I need?
Mistral's connector docs name no minimum plan, and its pricing page shows Custom MCP connectors (beta) with a check mark under Free, Pro, Team and Enterprise. Adding one requires an administrator, and on Free, Pro and Student plans the account owner is the administrator by default.
Can I connect Le Chat to Google Ads for free?
Partly: adding the connector costs nothing and Mistral's pricing page marks custom MCP connectors (beta) on the Free plan, but the Google Ads tools need an active Ryze AI plan or trial. Paid Ads comes with a 7-day free trial.
Can Le Chat change my Google Ads account?
Yes, if the connected Google login has standard or admin access. Write functions can create campaigns, adjust budgets, bids and keywords, and apply Google recommendations. Work stops for approval before anything that creates, modifies or deletes unless that function is on Always allow, and Mistral suggests manual approval for writes.
Can Le Chat delete Google Ads items?
A single dedicated tool removes items, and its description asks the agent to run it only against a list you approved item by item. Google Ads offers no undo for removals. For zero removals, connect a Google login with read access only.
Do I need a client ID and secret?
No. Mistral detects the authentication method itself, and Ryze AI supports OAuth 2.1 with dynamic client registration. Leave any credential fields empty and complete the sign-in when prompted.
Can I use more than one Google Ads account?
Yes. One Google login reaches every account it can open, client accounts under a manager login included. For a second login use Add one more account on the Google Ads card. Over MCP, connection_id picks a login and loginCustomerId is needed for client accounts under a manager. Separate clients belong in separate workspaces.
Why do the Google Ads tools not show up in Le Chat?
Open a fresh chat first, then try Refresh tools on the Functions tab of the Ryze AI card. If the tools are still missing, remove the Ryze AI connector, add it back and check that the Google Ads card in Ryze AI reads Connected. Mistral says custom connectors do not yet support dynamic tool discovery.
How much does it cost to connect Le Chat to Google Ads?
Connecting is free. The Google Ads functions need an active Ryze AI plan or trial: Paid Ads costs $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial and Agency $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Google Ads from Le Chat?
Remove the Ryze AI connector from Connectors in Mistral Vibe. To cut Google Ads off at the source, disconnect the login on the Google Ads card in Ryze AI or revoke access on your Google Account permissions page.