By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Le Chat to Meta Ads is the Ryze AI connector. Connect Meta Ads in a Ryze AI workspace with your Meta login. 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 Meta Ads and click Connect
- Sign in to Meta with a login that opens 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 Meta Ads at a glance
| Fact | Detail |
|---|---|
| Main way | The Ryze AI connector, added to Mistral Vibe as a Custom MCP Connector |
| Address to enter | https://connector.get-ryze.ai/mcp |
| Sign-in | Meta once in Ryze AI, then Ryze AI from Mistral, which detects OAuth 2.1 with dynamic client registration. No client ID or secret to type |
| Meta Ads tools | 10: 7 read, 2 write, 1 delete |
| Changes to ads | Yes, if the Meta login may edit. Mistral Vibe asks before any call that creates, modifies, sends, posts or deletes |
| Mistral requirement | An administrator adds the connector. On Free, Pro and Student the account owner is the administrator. No minimum plan is named |
| Ryze AI price | Paid Ads, $89 per month with a 7-day free trial. The connector is free |
| Meta's own server | https://mcp.facebook.com/ads, open beta. Meta's pages do not name Le Chat, and not every ad account has access yet |
| Out of reach | Organic posts, Page comments, lead export, restoring deleted objects |
| Last tested | Meta Ads calls on November 14, 2026, sent from Claude Code. Nothing was run inside Mistral Vibe |
Before you start
- Administrator rights in Mistral. Mistral's docs call adding a custom MCP connector an administrator-only action, and on Free, Pro and Student plans the account owner is the administrator by default. The docs name no minimum plan. On a team or organization account, ask an administrator to add it.
- A Meta login that can open an ad account. The Ryze AI help center asks for a Meta Business account with an ad account, at least Advertiser access on it, Admin access before changes are allowed, and ideally access through Meta Business Manager. Meta's role table lets an Advertiser create and edit ads as well. You use this login on the Ryze AI Connect step.
- A Ryze AI workspace on a plan or free trial. Paid Ads costs $89 per month with a 7-day free trial, and annual billing takes 30% off the first year. Adding the connector is free; the Meta Ads tools run only with an active plan or trial.
- A server reachable over HTTPS. Mistral requires a valid TLS certificate. The Ryze AI address meets that, so enter it exactly as written.
How to connect Le Chat to Meta Ads
Setup has two parts. Meta Ads is linked inside Ryze AI first, and then Mistral Vibe gets the address of the Ryze AI connector. The Mistral half follows Mistral's MCP connectors docs. Ryze AI has no help center page for Mistral, and nobody ran the sign-in inside Mistral Vibe while this guide was written, so check the errors section below if a screen looks different.
Connect Meta Ads in Ryze AI
Log in to Ryze AI or create an account. In the left sidebar choose Integrations, look under Advertising for Meta Ads and click Connect.
Sign in to Meta and approve every permission
Log in to Meta and approve the request with every permission left checked. The Meta Ads card then reads Connected. You pick no ad account here, because Ryze AI can see every ad account that login opens.
Open Connectors in Mistral Vibe
Go to chat.mistral.ai (the address stayed the same when 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 by itself. Ryze AI uses OAuth 2.1 with dynamic client registration, so no client ID or secret is entered.
Finish the Ryze AI sign-in
Complete the Ryze AI sign-in when Mistral prompts, choose the workspaces that hold your Meta Ads connection and click Allow connection. Then start a new chat and ask a Meta Ads question.
There is no Ryze AI help center page for Mistral Vibe. The Ryze AI Meta Ads guide covers the Meta sign-in on the Ryze AI side.
Sources: Mistral docs: MCP connectors, Mistral docs: Connectors, Mistral help: Le Chat is now Vibe, Ryze AI Meta Ads guide. Checked November 15, 2026.
Approvals and Always allow
Mistral lets each user decide how much a 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 the read functions you want to run without a prompt each time, such as the account list or the Insights query.
- Leave Always allow off for meta_ads__runGraphWrite, meta_ads__uploadImageFromUrl and meta_ads__runGraphDelete, so Mistral asks before each one.
- Use Refresh tools on the same tab to reload the function list after Ryze AI changes it.
Mistral's Safety and approvals page says Work pauses before anything that creates, modifies, sends, posts or deletes, and gives three answers: Continue for that one action, Always allow for that function until the session ends, or Decline. The toggles on the Functions tab belong to each user, so your choices do not change a teammate's settings. Mistral advises keeping write functions on manual approval until you trust the connector. For a connection that can never change an ad account, connect a Meta login with read access only.
Sources: Mistral docs: MCP connectors, Mistral docs: Safety and approvals. Checked November 15, 2026.
Vibe Work and Vibe Code
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 describes 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 in 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, 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 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 | The connector docs name no minimum plan. Mistral's pricing page shows a check mark for the beta Custom MCP connectors feature under Free, Pro, Team and Enterprise |
| 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 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, Mistral docs: MCP connectors, Mistral docs: Safety and approvals, Mistral docs: Admin Panel connectors, Mistral docs: Vibe Code MCP servers, Mistral pricing. Checked November 15, 2026.
Meta Ads access and permissions
Three gates sit between Mistral Vibe and your ads. Mistral decides who may add the connector and which calls ask first, Ryze AI decides which ad accounts are visible, and Meta sets what the login may do. Ryze AI does not hand out roles on ad accounts.
- Which ad accounts
- Ryze AI reaches exactly the ad accounts the Meta login opens, and no others. On the Meta Ads card, Agent default accounts sets which ones the agent starts with; any other one still works when a prompt names it.
- What role the login has
- The Ryze AI help center asks for at least Advertiser access, and Admin access to allow changes. Meta's role table gives Advertisers the right to create and edit ads and keeps payment and people management for Admins. To rule out edits entirely, connect a Meta login that can only read, which in Meta's table is the Analyst role.
- What Mistral lets through
- Work asks before a call that creates, modifies, sends, posts or deletes. In an organization, an admin can set the Connectors setting to Allowed, Restricted or Blocked per workspace, so an admin may have switched custom connectors off for yours.
On the Meta step, Ryze AI requests 11 permissions: ads_management, ads_read, business_management, pages_show_list, pages_read_engagement, pages_manage_ads, leads_retrieval, catalog_management, instagram_basic, instagram_manage_comments and public_profile. Keep all of them checked. Meta's authorization guide ties ads_read to reading ad reports for accounts you own or were given, and ads_management to reading and managing the ads in those accounts.
The 11 Meta permissions of the default connection
The 11 permissions group into seven areas. The list comes from the Ryze AI app and was not read off a live consent screen for this guide. The default connection uses no key or token that you handle: Ryze AI keeps the user access your Meta sign-in creates.
| Area | Permissions | What Meta says they allow, with Ryze AI notes |
|---|---|---|
| Ads and reports | ads_read, ads_management | Insights report data, and reading and managing ad accounts the person owns or was given |
| Business assets | business_management | Business Manager API reads and writes, such as claiming an ad account |
| Facebook Pages | pages_show_list, pages_read_engagement, pages_manage_ads | The Pages a person manages, a Page's own posts and insights, and the ads tied to a Page |
| Lead ads | leads_retrieval | All data a lead form collected. The Ryze AI tools only list forms |
| Catalogs | catalog_management | Managing business product catalogs. None of the 10 tools is a catalog tool |
| instagram_basic, instagram_manage_comments | Profile and media, and comments on the Instagram account linked to a Page. The Ryze AI facts list no job that uses the comment permission | |
| Profile | public_profile | Default public profile fields, granted to every app |
Four permissions are not requested. pages_manage_posts and instagram_content_publish are missing, so organic Facebook Page and Instagram posts cannot be published from Mistral Vibe. pages_read_user_content is missing, so comments people leave on a Page cannot be read. ads_mcp_management, which Meta requires for its own ads MCP server, is missing too, because Ryze AI calls the Marketing API directly.
Meta's ad account roles
Meta's Business Help Center describes three ad account roles. Admin views ads and reports, creates and edits ads, edits the payment method and manages admin permissions. Advertiser has the same rights minus payment and other people's access. Analyst views ads and reports and nothing else. Ads that run for a Page also need full control or partial access (Ads) on that Page, and Instagram ads need a professional Instagram account linked to it.
Sources: Meta permissions reference, Meta Marketing API authorization, Meta ad account roles, Ryze AI Meta Ads guide. Checked November 14, 2026.
Removing access
You can cut access in two places. Click View on the Meta Ads card in Ryze AI and disconnect the login, or open Connectors, My Connectors in Mistral Vibe and remove the Ryze AI connector. Meta access lapses more often than Google access does: after a two-factor change or a Business Manager role change, Ryze AI shows Reconnect needed.
What Le Chat can do in Meta Ads
The Ryze AI connector gives Mistral Vibe 10 Meta Ads tools: 7 that read, 2 that write and 1 that deletes. Mistral calls an action of a connector a function; this page says tool. Each tool acts as the Meta login you connected, and over MCP each accepts an optional connection_id to choose between logins.
| Tool | Type | What it does |
|---|---|---|
| meta_ads__listAdAccounts | Read | Lists every ad account the connected Meta user can open, with id, name and currency. |
| meta_ads__getAccountSummary | Read | Returns aggregate metrics for one ad account on Meta's default attribution window. |
| meta_ads__runRawInsights | Read | Runs a raw Insights query at account, campaign, ad set or ad level, with the breakdowns, filters and attribution windows you ask for. |
| meta_ads__listCreatives | Read | Lists the ad creatives in an ad account. |
| meta_ads__getCreative | Read | Gets one creative by id. |
| meta_ads__listLeadForms | Read | Lists the lead generation forms on a Facebook Page. |
| meta_ads__runGraphRead | Read | Reads any Graph API object or edge, such as paused campaigns, targeting specs or an ad account's activity log. |
| meta_ads__runGraphWrite | Write | Creates or updates campaigns, ad sets, ads, creatives and other objects through the Graph API. |
| meta_ads__uploadImageFromUrl | Write | Uploads an image from a URL to an ad account and returns the image hash a creative uses. |
| meta_ads__runGraphDelete | Delete | Deletes or archives Meta objects. Its description says it is meant for an explicit, 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 two write tools and the delete tool. Mistral's pages do not say whether a custom connector's read functions ask by default. The Ryze AI chat is a separate place, and its Tool approvals setting starts on Skip all approvals. Archived or deleted Meta objects cannot be restored through Ryze AI.
Limits in numbers
Most Meta limits below are counted per ad account. Their size depends on whether the calling app has Limited (development) or Full access, and the Ryze AI facts do not say which one the Ryze AI Meta app holds, so the table gives both. Mistral's connector docs print no cap on the number of tools or calls.
| Limit | Number |
|---|---|
| Call score | 1 point per read, 3 per write, decaying over 300 seconds. Ceiling 60 (development) or 9,000 (Full access), then a pause of 300 or 60 seconds |
| Ads management calls per hour | Per ad account: 300 (development) or 100,000 (Full access), plus 40 per active ad. Error 80004 above that |
| Insights calls per hour | Per ad account: 600 (development) or 190,000 (Full access), plus 400 per active ad, minus 0.001 per user error. Error 80000 above that |
| Edits to the same object | One every 30 seconds per app by default. Error 613, subcode 4841018 |
| Ad set budget changes | 4 an hour, then budget changes on that ad set are blocked for an hour. Error 613, subcode 1487632 |
| How far back reports go | 37 months. An earlier start date fails with error 3018, as the test showed |
| Time slices | time_increment of 1 to 90 days, monthly or all_days. 91 was refused in the test |
| Freshness | Insights refresh every 15 minutes and stop changing 28 days after they are reported |
| Fields in one Graph read | 2,048 characters in meta_ads__runGraphRead, enforced by the connector in the test |
| Connector name in Mistral | Unique, with no spaces or special characters |
Sources: Meta Marketing API rate limiting, Meta Graph API rate limiting, Meta ad account Insights reference, Meta Insights best practices, Mistral docs: MCP connectors. Checked November 14, 2026.
What the Meta Ads tools returned in the test
On November 14, 2026, Claude Code sent 11 Meta Ads calls to the live Ryze AI connector. It reaches the same server and the same 10 tools that Mistral Vibe would. One call was a plain read, and the other ten were built to fail so that Meta's error text could be collected. The ad accounts are real, so the table lists outcomes and no values.
| What was sent | Tool | What came back |
|---|---|---|
| Ad account list | meta_ads__listAdAccounts | Worked: id, account_id, name and currency per account. Values not shown |
| Campaigns edge, made-up field | meta_ads__runGraphRead | No error. The field was ignored; ids and paging cursors came back |
| Ad account node, made-up field | meta_ads__runGraphRead | No error. Only the id came back |
| Object ID that does not exist | meta_ads__runGraphRead | Meta code 100, subcode 33 |
| Made-up edge | meta_ads__runGraphRead | Meta code 2500 |
| Fields value of 2,100 characters | meta_ads__runGraphRead | Connector: invalid_arguments, maximum 2048 |
| Made-up Insights field | meta_ads__runRawInsights | Meta code 100 |
| Ad account the login cannot open | meta_ads__runRawInsights | Connector: not_allowed, Meta error 200 |
| Attribution window 99d_click | meta_ads__runRawInsights | Meta code 100, with the 26 accepted windows |
| January 2020 report | meta_ads__runRawInsights | Meta code 3018, the 37-month rule |
| timeIncrement of 91 | meta_ads__runRawInsights | Meta code 100, maximum 90 |
One result changes how you should word prompts. The description of meta_ads__runGraphRead says an unknown field fails the whole read, yet both Graph reads above ignored the invented field. A misspelled Graph field can therefore come back as a thin answer with no error, while a misspelled Insights field does raise one.
First 3 prompts to run
Each prompt below says what it asks for and which tools it uses. The answers depend on your own ad accounts, so no sample figures appear here.
1. List the ad accounts, then read one
Use the RyzeAI connector to list the Meta ad accounts this login can open, then show spend, ROAS and CTR for the first one over the last 30 days.
Tools used: meta_ads__listAdAccounts, meta_ads__getAccountSummary
What comes back: Each reachable ad account with its id, name and currency, then totals for the account you chose on Meta's default attribution window.
2. Split results by age and device
With RyzeAI, run an ad level Insights query for the last 14 days broken down by age and device, using a 7-day click attribution window.
Tools used: meta_ads__runRawInsights
What comes back: Ad rows split by the breakdowns you asked for. The tool accepts breakdowns such as age, gender, country, device and placement, and attribution windows of your choice.
3. See who changed the account
Ask RyzeAI to read this ad account's activity log, list the latest campaign and budget changes, and then list the paused campaigns.
Tools used: meta_ads__runGraphRead
What comes back: Activity log entries that show who changed what, then the paused campaigns, both read over the Graph API.
Start with prompts that only read. When Mistral asks permission for a write, check the action it describes before you click Continue. Once you trust the setup, ask for changes such as pausing a campaign or swapping a creative and name the exact campaign or ad.
10 jobs to hand to Le Chat
Ten jobs to give Le Chat once the connector is in, each with its Ryze AI tool. Name the RyzeAI connector in the request, or pick it from the Tools menu in the chat box. Only the account list ran successfully for this guide; the other rows rest on the Ryze AI facts and on Meta's documentation.
| Job | Ask Le Chat | Tool | Works on the default connection |
|---|---|---|---|
| Account inventory | Which ad accounts can this login open, and in which currency? | meta_ads__listAdAccounts | Yes. It worked in the test |
| Monthly totals | Spend, ROAS and CTR for last month in the account I name. | meta_ads__getAccountSummary | Yes, on Meta's default attribution window only |
| Age and placement split | Last month by age and placement at ad set level, 7-day click. | meta_ads__runRawInsights | Yes, for start dates within 37 months |
| Creative review | List this account's creatives, then open the one whose id I paste. | meta_ads__listCreatives, meta_ads__getCreative | Yes |
| Lead form check | Which lead forms sit on the Page with this ID? | meta_ads__listLeadForms | Yes, with a role on that Page. Forms only |
| Who changed what | Budget and status changes from this account's activity log in the past week. | meta_ads__runGraphRead | Yes |
| Pause or budget edit | Pause the ad set I name and change the daily budget of the other one to my figure. | meta_ads__runGraphWrite | Yes, with a role that may edit. 4 budget changes per ad set per hour |
| New image for an ad | Upload the image at this URL and give me its image hash. | meta_ads__uploadImageFromUrl | Yes, with a role that may edit |
| Clean-up | Archive the three paused campaigns I list, with one confirmation each. | meta_ads__runGraphDelete | Yes, from a list approved item by item. No undo |
| Lead export | Download the leads from my lead form as a table. | None | No. No Ryze AI tool exports leads |
5 ways to connect Le Chat to Meta Ads
A custom connector in Vibe Work has to point at a remote MCP server over HTTPS, and Work cannot start a local command. Five ways into Meta Ads fit that shape. The Ryze AI connector is the main way: one Meta approval in Ryze AI, one address in Mistral and 10 tools for reports, creatives and campaign changes. None of the other four vendors names Le Chat or Mistral on the pages read on November 14, 2026, and none was tried in Vibe Work.
| Way | Runs where | Setup in Mistral Vibe | What it reaches in Meta 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. Meta is connected once in Ryze AI | 10 tools: account list, summaries, raw Insights with your own attribution windows, creatives, lead form lists, Graph reads and writes, image upload, and a separate delete tool | Paid Ads $89 per month, 7-day free trial. The connector is free |
| Meta ads MCP server | Hosted by Meta at https://mcp.facebook.com/ads, open beta | Meta says to enter one URL in your AI tool and sign in with Facebook, and says the server works with any MCP-compatible agent. Its OAuth details list a registration endpoint, which matches the sign-in type Mistral detects. Meta prints no Mistral steps and this was not tried | Reporting, campaign creation and editing, catalogs, datasets, A/B tests, lift studies and the activity log: 88 tool names on Meta's tool pages. New entities start paused | No additional cost from Meta. Not every ad account has access yet |
| Pipeboard Meta Ads MCP | Hosted at https://meta-ads.mcp.pipeboard.co/, or self-hosted with your own Meta app | Connect Facebook Ads in a Pipeboard account, then add the address. The README says an API token can be appended to the URL to skip the interactive login, and shows steps for Claude and Cursor only | 42 tools in the README's table, 28 in its numbered list. Writes ask first and new campaigns start paused | Free: 30 tool executions a week, 2 ad account slots. Pro US$29.90 per month |
| Windsor.ai (Windsor MCP) | Hosted | Add Facebook Ads as a data source in Windsor.ai, then add Windsor MCP as a remote server. Its page lists Claude, ChatGPT, Microsoft Copilot, Gemini Enterprise and Perplexity "and other clients that support remote MCP servers" | 656 metrics and 212 dimensions, plus 20 write actions that each wait for your approval. No deletes, catalogs, custom audiences or pixels | Forever Free: 1 account, past 30 days. Basic $23 per month |
| Coupler.io Facebook Ads MCP | Hosted | Build a Facebook Ads data flow on a refresh schedule. Its Custom MCP route gives a server URL and a Bearer token, a sign-in type Mistral detects, but Mistral's page does not say where a token is typed | Read-only answers from synced data | Free: 1 account, manual refresh. Starter $32 per month |
Other Meta Ads options left out of the table
- Meta's server with an access token. Meta also accepts a token in an Authorization: Bearer header. Mistral detects Bearer auth, but its pages do not say where a custom connector takes the token, and Meta's own-developer-app steps cover Claude Code and ChatGPT.
- Meta's Ads CLI. A terminal program for macOS and Linux that uses a system user token. It is not an MCP server, and its pages name no assistant.
- Composio (Metaads toolkit). 99 tools behind a Meta OAuth app you register. Its page names Claude Code, Cursor, ChatGPT, Claude Cowork, Antigravity, Codex, VS Code, OpenCode, OpenClaw, Grok Bot, Grok Build, Kimi Code, Muse and Hermes, not Le Chat.
- Zapier MCP. No Meta Ads MCP page, and its three Meta-related apps neither read campaign results nor edit campaigns. Its client lists name Claude, Claude Code, ChatGPT, Cursor, Codex, Gemini Enterprise, Grok, Grok Bot, VS Code and Windsurf among others; Le Chat was not checked on that list.
- Meta AI business assistant. It works inside Ads Manager only, so Mistral Vibe cannot reach it.
- Mistral's connector directory. Vibe Work also offers Featured Connectors and an MCP Connectors directory. This guide did not check whether either holds a Meta Ads connector.
Which one to pick
Ryze AI is the best way to connect Le Chat to Meta Ads when one chat should read Insights with your own attribution windows and also change campaigns, with two caveats: the tools need an active Ryze AI plan or trial, and the connection cannot publish organic posts, read Page comments, export leads or restore deleted objects. Meta's own server costs nothing extra and adds catalog, dataset and lift study tools, but Meta does not name Le Chat, and its beta has not reached every ad account. Pipeboard has a free hosted tier, Windsor.ai waits for your approval on each of its 20 write actions, and Coupler.io suits read-only questions on scheduled data.
Sources: Meta ads MCP server page, Meta ads MCP server overview, Meta ads MCP server get started, Meta ads AI connectors announcement, Meta Ads CLI overview, Pipeboard meta-ads-mcp README, Pipeboard pricing, Windsor.ai Facebook Ads MCP, Windsor.ai pricing, Coupler.io Facebook Ads MCP, Coupler.io pricing, Composio Metaads toolkit, Zapier MCP quickstart, Mistral docs: MCP connectors, Ryze AI Meta Ads guide. Checked November 14 and 15, 2026.
Le Chat, Meta Ads and MCP: dates that matter
| Date | What happened |
|---|---|
| June 10, 2025 | Meta's Insights API dropped reach with breakdowns for start dates over 13 months back and began following each ad set's attribution setting. |
| 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. |
| April 29, 2026 | Meta opened the beta of its ads AI connectors, the ads MCP server and the Ads CLI. |
| 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. |
| July 16, 2026 | Meta's server began to accept your own developer app, and ads MCP server rules arrived. |
| September 22, 2026 | Chat and Work merged into one Vibe experience. Enterprise organizations move from October 1, 2026, within about six months. |
| November 4, 2026 | Meta released Marketing API v27.0, current on November 14, 2026. |
| November 10, 2026 | Marketing API v24.0 stopped being available. |
Sources: Meta Insights best practices, Meta ads AI connectors announcement, Meta for Developers, July 16, 2026, Meta Marketing API v27.0, Meta Marketing API versions, Mistral changelog, Mistral news, September 2, 2025, Mistral news, May 28, 2026, Mistral news, June 24, 2026. Checked November 14 and 15, 2026.
How this guide was tested
Two things stand behind this guide: calls to the Ryze AI connector's Meta Ads tools on November 14, 2026, and the vendors' own pages as read on November 14 (Meta) and November 15 (Mistral). Nothing in an ad account was changed.
| What was run | What came back |
|---|---|
| The Meta Ads tool list (November 14, 2026) | All 10 names loaded: 7 read, 2 write, 1 delete, each with an optional connection_id. |
| meta_ads__listAdAccounts (November 14, 2026) | Worked. The accounts are real, so nothing from them is printed. |
| Ten calls meant to fail (November 14, 2026) | Eight returned the error messages quoted below. Two Graph reads with an invented field returned ids and no error. |
| Rate-limit headers (November 14, 2026) | No answer carried one of Meta's usage headers or a usage percentage. |
| Meta's own server without a sign-in (November 14, 2026) | Not a Ryze AI call. https://mcp.facebook.com/ads answered HTTP 401, named 10 permissions and listed a registration endpoint. |
| One Search Console call (November 14, 2026) | Not a Meta Ads call. It supplied search phrases for some FAQ questions; figures withheld. |
Not run: 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 10 tools. meta_ads__getAccountSummary, meta_ads__listCreatives, meta_ads__getCreative and meta_ads__listLeadForms were not called, and no Insights report returned figures, because those answers hold account data. The write, upload and delete tools were not run, since they change the ad account. Meta's server, its Ads CLI, Pipeboard, Windsor.ai and Coupler.io were not used with a sign-in.
Le Chat and Meta Ads errors and fixes
Exact error messages from the test
Meta and the Ryze AI connector returned these messages on November 14, 2026, to calls sent from Claude Code. They are copied as returned, with the object ID replaced by <redacted>. If an answer in Le Chat quotes one, the row says what happened and what to ask next.
| Message | What it means | What to ask Le Chat |
|---|---|---|
| Unsupported get request. Object with ID '<redacted>' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api | Code 100, subcode 33: a wrong ID, or an object the login cannot see. Meta words both the same. | Ask Le Chat to list the campaigns or ad accounts first, then retry with an ID from that answer. |
| (#100) not_a_field_xyz is not valid for fields param. please check https://developers.facebook.com/docs/marketing-api/reference/ads-insights/ for all valid values | Code 100: no Insights field by that name. Per the tool description, roas is purchase_roas and status, placement and creative are not Insights fields. | Ask for the Insights field name, or have Le Chat read settings with meta_ads__runGraphRead. |
| Meta Graph error (code 200): (#200) Ad account owner has NOT grant ads_management or ads_read permission, refer to https://developers.facebook.com/docs/marketing-api/get-started/authorization/#permissions-and-features for details. | The login cannot open that ad account, or the ID has a typo. The connector labels it not_allowed. | Pick an ID from meta_ads__listAdAccounts, or give the login a role on the account in Business Manager. |
| (#100) action_attribution_windows[0] must be one of the following values: 1d_view, 7d_view, 28d_view, 1d_click, 7d_click, 28d_click, 1d_ev, dda, default, 7d_view_first_conversion, 28d_view_first_conversion, 7d_view_all_conversions, 28d_view_all_conversions, skan_view, skan_click, skan_click_second_postback, skan_view_second_postback, skan_click_third_postback, skan_view_third_postback, incrementality, incrementality_first_conversion, incrementality_all_conversions, custom, 1d_sequenced, 7d_sequenced, 28d_sequenced | Code 100: an unknown window name. The test sent 99d_click. | Ask again with 1d_click, 7d_click, 28d_click or 1d_view, the windows the tool description suggests. |
| (#3018) The start date of the time range cannot be beyond 37 months from the current date. The earliest start date available for this ad account is 2023-10-14. Set time_range or time_ranges to start on or after that date. | Code 3018: the test asked for January 2020, beyond the 37 months Meta keeps. The printed date is 37 months before the call. | Start the report inside the last 37 months. |
| (#100) Param name_placeholder must be a number less than or equal to 90 | Code 100: the test asked for 91-day slices. Meta prints name_placeholder in place of time_increment. | Ask for slices of 90 days or fewer, monthly or all_days. |
| Unknown path components: /not_an_edge_xyz | Code 2500: the object has no edge by that name. | Ask for a real edge such as campaigns, adsets, ads, adcreatives or activities. |
| Too big: expected string to have <=2048 characters | The Ryze AI connector stopped the call (invalid_arguments) before Meta saw it: the fields list passed 2,048 characters. | Ask for fewer fields per call, or split it into two calls. |
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 its 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.
- The connector name is rejected
- Mistral wants a unique name with no spaces or special characters. Use RyzeAI.
- The Meta Ads tools do not load
- Open a fresh chat, then click Refresh tools on the Functions tab of the Ryze AI card. If they are still missing, check that the Meta 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.
- Meta shows Reconnect needed
- Click Connect on the Meta Ads card again and approve every permission once more. A two-factor change or a new Business Manager role is the usual trigger.
- An ad account is missing from the results
- The connected Meta login has to be able to open that account. Ask its owner to give the login a role in Business Manager, or attach another login with Add one more account on the Meta Ads card.
- A change is refused
- The login may only be able to read, for example with Meta's Analyst role, and the Ryze AI help center asks for Admin access before changes. Roles are set in Meta, so the account owner has to raise the role there.
- A quick second edit to the same object fails
- Meta allows one edit per object every 30 seconds for each app by default and answers faster attempts with error 613, subcode 4841018. Wait half a minute and ask again.
- Mistral says a subscription is required
- The Meta Ads tools work only on an active Ryze AI plan or free trial. Start the trial, then repeat the request.
Terms on this page
- Custom MCP Connector
- What Mistral calls an MCP server that you add by its HTTPS address on the Connectors page.
- MCP
- The Model Context Protocol, an open standard through which AI models reach outside data and apps.
- Ad account
- Meta's container for billing and reporting. Campaigns, creatives and access roles all belong to one, and its ID is act_ followed by a number.
- Insights API
- The reporting part of Meta's Marketing API, available on ad accounts, campaigns, ad sets and ads. It needs the ads_read permission.
- Attribution window
- The span after a click or a view during which a conversion still counts for an ad, such as 7 days after a click.
- Business Use Case rate limit
- Meta's hourly quota for Marketing API calls, kept per ad account and per kind of work: ads management, Insights, custom audiences and catalogs.
- Ads MCP server rules
- Settings in Meta Business Suite that allow or block what an AI agent may do on an ad account or catalog through Meta's own server. Meta says they are in limited availability.
Sources: Mistral docs: MCP connectors, Meta ad account reference, Meta Insights API, Meta ad account Insights reference, Meta Graph API rate limiting, Meta ads MCP server rules. Checked November 14, 2026.
Frequently asked questions
How do I connect Le Chat to Meta Ads?
Link Meta Ads in a Ryze AI workspace under Integrations by approving every Meta permission, then add https://connector.get-ryze.ai/mcp in Mistral Vibe (formerly Le Chat). The path is Connectors, + Add Connector, Custom MCP Connector; enter a name such as RyzeAI and the URL, click Connect and finish the Ryze AI sign-in.
What is the Meta 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. Meta's own server sits at https://mcp.facebook.com/ads; Meta's pages do not name Le Chat, and that route was not tried for this guide.
Is there a Le Chat Meta Ads connector?
Mistral lets an administrator add any remote MCP server by URL as a Custom MCP Connector, and the Ryze AI connector is added that way. Whether Mistral's own directory lists a Meta Ads connector was not checked.
Does Meta's ads MCP server work with Le Chat?
Meta says its server works with any MCP-compatible AI agent and names ChatGPT, Claude and Perplexity as supported AI tools; it does not name Le Chat or give Mistral steps. The server is in open beta, and Meta says not all ad accounts have access yet.
Which Meta Ads connector should I use with Le Chat?
Ryze AI is the best Meta Ads connector for Le Chat when you want raw Insights with your own attribution windows plus Graph reads and writes behind one URL, with the caveat that it needs a Ryze AI plan or trial and cannot post organic content, read Page comments or export leads. Meta's own server costs nothing extra but is in beta, and Meta does not name Le Chat.
Do I need a paid Mistral plan?
Mistral's connector docs name no minimum plan. They say an administrator has to add a custom MCP connector, and on Free, Pro and Student plans the account owner is the administrator. Mistral's pricing page marks Custom MCP connectors, labeled beta, on Free, Pro, Team and Enterprise.
Can Le Chat change my Meta ad account?
Yes, if the Meta login you connected may edit that ad account. The write tools create or update campaigns, ad sets, ads and creatives and upload images. Mistral asks before a call that creates, modifies, sends, posts or deletes, so read the prompt before you click Continue.
Can Le Chat delete Meta Ads campaigns?
Yes, through one tool built for deleting or archiving Meta objects, whose description reserves it for a list you approved item by item. Ryze AI cannot bring back an archived or deleted object. For no changes of any kind, connect a Meta login with read access only.
How do I stop Le Chat from running write tools without asking?
Open Connectors, My Connectors, the Ryze AI card and its Functions tab, and leave Always allow off for the write and delete functions. Mistral advises keeping write functions on manual approval.
Which sign-in does Mistral use for Ryze AI?
Mistral detects it from the URL. Ryze AI uses OAuth 2.1 with dynamic client registration, so there is no client ID or secret to type. You sign in to Ryze AI, choose workspaces and click Allow connection.
Can I use more than one Meta ad account?
Yes. A single Meta login reaches every ad account it can open, and Add one more account on the Meta Ads card attaches another login. Each Meta Ads tool takes an optional connection_id, and separate clients belong in separate Ryze AI workspaces.
Can Le Chat read comments or publish posts on my Facebook Page?
No. The Ryze AI Meta app holds none of pages_manage_posts, instagram_content_publish and pages_read_user_content, so organic Page and Instagram posts and Page comments are out of reach. The tools work on ad accounts, creatives and lead forms.
Can Le Chat look up ads in the Meta Ad Library?
Yes, through a separate Ryze AI tool, native__search_ad_library, which searches Meta's public Ad Library and needs no Meta connection. It is not one of the 10 Meta Ads tools, and it was not called for this guide.
Why do the Meta Ads tools not show up in Le Chat?
Open a new chat first, then click Refresh tools on the Functions tab of the Ryze AI card. If they are still missing, confirm that Ryze AI lists Meta Ads as Connected, then remove the connector and add it again.
How much does it cost to connect Le Chat to Meta Ads?
Adding the connector is free, and the Meta Ads tools need an active Ryze AI plan or trial. Paid Ads is $89 per month with a 7-day free trial, Agency is $279 per month, and annual billing takes 30% off the first year.