Eulerian MCP Integration Guide for Mistral Vibe
EULERIAN MCP
- Mistral integration guide
- For users without advanced technical knowledge
- Custom connector with OAuth · Mistral Studio · Vibe
1. What it is and how it differs from the other versions
This guide connects Mistral directly to Eulerian's remote MCP server. Authentication is handled through OAuth 2.1: you install nothing, you don't use the terminal and you never have to paste a token. The main difference from Claude or ChatGPT is that in Mistral the custom connector is created from Mistral Studio ( console.mistral.ai ), not directly from Vibe ( chat.mistral.ai ). Once created, it becomes available in Vibe under Admin > Connectors.
Is this the same as Claude or ChatGPT?The principle is identical: a remote endpoint + OAuth sign-in, with nothing to install and Mistral never seeing your password. What changes is where the connector is added: in Mistral you do it from Studio ( console.mistral.ai ) and then use it in Vibe.
What you can do with it:
- Check last week's paid search campaign performance with a single sentence.
- Discover which media channels drove the most conversions this month.
- Analyse the customer journey of your highest-converting segment.
- Get analytics insights without exporting data manually.
2. Before you begin
You need these four things before continuing:
1
A Mistral account
It can be set up from a free account. Creating custom MCP connectors is done in Mistral Studio ( console.mistral.ai ), which is part of the same account as Vibe.
2
Access to Mistral Studio
Today, custom connectors are created in Studio (a "Preview" feature). They can't yet be created directly from Vibe: you only see and use them once created. On team/organisation accounts, this may require administrator permissions.
3
Eulerian's remote MCP endpoint URL
Eulerian provides it; it looks like https://your-instance.api.eulerian.com/mcp . It must be reachable over the internet and over HTTPS with a valid TLS certificate, because the connection originates from Mistral's servers (not from your computer).
4
Your Eulerian credentials
Your Eulerian username and password. You'll sign in during the OAuth step. Unlike the desktop/CLI method, there is NO API token to paste here.
This may change (and depends on your account type)Mistral states that custom (MCP) connectors are available in Mistral Studio and will come to Vibe soon; the location and requirements may change. For team and organisation accounts, check Mistral's specific documentation, as management may be centralised.
3. Step-by-step installation
Step 1 From Vibe, open Mistral Studio
In Vibe ( chat.mistral.ai ), click the drop-down menu in the top-left corner and choose Studio. Mistral Studio opens at console.mistral.ai .
In Vibe, open the top-left menu and choose "Studio" (screenshots shown in Spanish UI).
Step 2 In Studio, open Connectors
Once in Mistral Studio, in the left-hand menu find the Context section and click Connectors. This is where you create and manage your connectors.
Mistral Studio: the "Connectors" item is under the "Context" block of the side menu.
Step 3 Click "+ Add connector"
On the Connectors page, click the "+ Add connector" button in the top-right corner. A window with the connector directory opens.
Studio's "Connectors" page, with the "+ Add connector" button.
Step 4 Switch to "Custom MCP Connector"
In the window that opens, switch from the Connector directory tab to the Custom MCP Connector tab (top-right).
Switch to the "Custom MCP Connector" tab to add Eulerian's server.
Step 5 Fill in the details and click "Create"
Enter a descriptive Title (for example "MCP Eulerian"). Under Server, paste the MCP endpoint URL Eulerian gave you. The Description is optional. The Authentication method is detected automatically and will be OAuth2.1. Click Create.
The custom connector form with the title, the server URL and OAuth2.1 (demo values shown).
No token to paste hereMistral auto-detects OAuth 2.1 from the URL. You sign in with your own Eulerian account; Mistral never sees your password, it only receives a limited, revocable access.
Step 6 Sign in to Eulerian and authorize
You'll be redirected to Eulerian's screen. Sign in with your Eulerian account and review the permissions requested by mistral-mcp-client (for example eulerian:reports.read). Click "Approve" to authorize. You're then returned to Mistral and the connector is set up; you'll find it in Vibe under Admin > Connectors as MCP Eulerian. You can now ask in natural language, for example:
Authorization at Eulerian: review mistral-mcp-client's permissions and click "Approve".
In Studio, "MCP Eulerian" appears under "Connected" as a custom connector.
In Vibe (Admin > Connectors), "MCP Eulerian" is listed as a custom connector, "Allowed".
Which Eulerian tools do you have access to?
Connection completeNothing installed and no tokens pasted. After you approve, Eulerian redirects you to callback.mistral.ai and the connector becomes available in your workspace. You can manage or disconnect it from Connectors at any time.
Step 7 Enable it in every conversation
Important: the connector isn't enabled automatically. In each Vibe conversation, click + (or type /) in the message box and, under Connectors, enable MCP Eulerian. If you don't, the assistant will reply that it has no access to the MCP.
In the message box, click "+" or "/" and enable "MCP Eulerian" under Connectors.
With the connector enabled, its icon is pinned to the message bar; you can now ask.
Do it in every new chatEnabling is per conversation. If you open a new chat and Vibe says it has no access to the MCP, enable "MCP Eulerian" again via "+" / "/" → Connectors.
4. Teams and organisations
When you create the connector, its Visibility is "Workspace": it's shared within your Mistral workspace. On team or organisation accounts, creating custom connectors and access to Studio may be controlled by an administrator:
- An administrator can enable (or restrict) the creation of custom connectors for the team.
- Once the connector is created, each user connects with their own Eulerian account, so they only access the data they can see in Eulerian.
Check Mistral's specific documentation for teams and organisations, and confirm the policy in force with your administrator before using real business data.
5. Other clients and notes
Because authentication uses OAuth 2.1 and is delegated to the MCP client, the same Eulerian remote endpoint works with other MCP-compatible clients (Claude, ChatGPT, etc.). Eulerian's part — endpoint URL, OAuth sign-in and authorization — is always the same; what changes is where each platform adds the connector.
Vibe (the app) vs Vibe CLI (terminal)This guide covers the Mistral app (Vibe + Studio), which connects through the interface with OAuth. The "Mistral Vibe CLI" is a separate integration configured via a configuration file and has its own guide. Don't confuse them: here you don't edit any file.
- MCP Connectors in Mistral (official docs): docs.mistral.ai/le-chat/knowledge-integrations/connectors/mcp-connectors
- Eulerian OAuth 2.1 documentation: doc.api.eulerian.com/#section/Introduction/OAuth-2.1-for-third-party-integrations
6. Security and best practices
OAuth instead of tokens
With the connector, no token is stored on your computer. You authenticate with your Eulerian account and Eulerian grants Mistral a limited access (for example, report reading only) that is revocable at any time.
Trusted connectors only
Mistral warns that MCP connectors aren't its products and it doesn't control third-party servers. Only add servers you trust: here, the developer is Eulerian. Always verify the origin of the URL.
Explicit, minimal permissions
Review the permissions shown on Eulerian's authorization screen (for example eulerian:reports.read) before clicking "Approve". Grant only what's needed and avoid write permissions if you won't use them.
Per-function permissions in Mistral
After creating the connector, each user can decide in Studio whether Mistral asks for permission every time it calls a function or pre-authorizes it ("Always Allow"). Pre-authorize only the read functions you use often and keep write functions on manual approval.
Validate with your IT department
Before using real business data, confirm with IT which AI platforms are approved. On teams/organisations, centralised connector management makes this control easier.
7. If something doesn't work
I can't see "+ Add connector" or "Custom MCP Connector"
Remember that custom connectors are created in Mistral Studio ( console.mistral.ai ), not in Vibe. On teams/organisations it may require administrator permissions.
"MCP connection requires additional information or is invalid"
Check the server URL: use the correct path (usually /mcp) and make sure it responds over HTTPS with a valid TLS certificate.
The connection fails or doesn't reach the server
The endpoint must be reachable over the internet: the connection leaves Mistral's servers, not your computer. If the server is behind a firewall or VPN, it won't connect.
Eulerian rejects the sign-in
Use your Eulerian credentials (not your Mistral ones). If you have access to several grids, use the URL with the correct parameter Eulerian indicated.
"Permission denied" after authorizing
On Eulerian's authorization screen you must click "Approve" (not "Deny"). If you clicked "Deny", repeat the create/connect step.
I can't see the connector in Vibe
Once created in Studio, it appears in Vibe under Admin > Connectors as a custom connector. Enable it in the conversation before asking.
8. Additional resources
- MCP Connectors in Mistral (official docs): docs.mistral.ai/le-chat/knowledge-integrations/connectors/mcp-connectors
- Eulerian OAuth 2.1 (third-party integrations): doc.api.eulerian.com/#section/Introduction/OAuth-2.1-for-third-party-integrations
- Eulerian MCP Server documentation: doc.eulerian.com/p/NhupKnGmQtUv_E/MCP-Server
- GitHub repository: github.com/EulerianTechnologies/eulerian-marketing-platform-mcp