- Integration guide — Other clients (OAuth)
- For users without advanced technical knowledge
- Remote connector with OAuth 2.1 · valid for any MCP-compatible client
Almost every MCP-compatible AI assistant connects to Eulerian the same way: you add a with Eulerian's MCP server URL and sign in via . The only thing that changes from one client to another is you add that connector. This general guide describes the common process; if you use Claude, ChatGPT, Gemini or Mistral, you also have a dedicated, illustrated guide.
The pattern common to all clients: a remote connector + OAuth sign-in at Eulerian.
A remote endpoint + OAuth sign-in: nothing to install, no terminal, no token to paste, and the client never sees your password. Eulerian grants only a limited, revocable access.
To connect with this method, the AI client must meet these criteria:
- Supports (custom connectors), not just local servers.
- Supports as an authentication method; ideally with dynamic client registration, so you don't have to create a Client ID/Secret by hand.
- Lets you enter a (remote endpoint) reachable over .
- The connection originates from the AI provider's servers, so the endpoint must be (not behind a firewall or VPN).
- Uses MCP's standard transport ().
The connector relies on Eulerian's MCP server, developed by Eulerian. It exposes the platform's tools and delegates authentication to OAuth 2.1, so each user only accesses the data their Eulerian account is allowed to see.
As examples, these clients currently meet the requirements above. Eulerian's part (endpoint + OAuth) is identical; only where you add the connector changes:
Settings → Connectors (or one-click .dxt extension on desktop)
Settings → Apps → Advanced settings → Developer mode
Gemini console/admin, depending on edition (verify)
Mistral Studio → Connectors; enable per conversation
Client interface or configuration file
Availability and menu names may change over time and depend on your plan or organisation. If a client isn't listed here, check its documentation to confirm it meets the requirements in Section 2.
You need these items before continuing:
An assistant that meets the requirements in Section 2 (remote MCP + OAuth 2.1).
It's your Eulerian API endpoint with /mcp appended. You find it in the Eulerian interface, within your account, under the "Eulerian API" section (see the box below).
Your Eulerian username and password. You'll sign in during the OAuth step. There is no API token to paste.
In some clients with team/enterprise accounts, an administrator must enable custom connectors or add the connector at the organisation level.
https://<your-Eulerian-API-endpoint>/mcp
In the Eulerian interface, within your account, go to the "Eulerian API" section: your API endpoint is shown there. The MCP server URL is that same endpoint with /mcp appended.
The steps are the same in any client; only where you find the connectors section in step 1 changes.
Find where connectors are added
In your AI client, look for the section (it may be called Connectors, Conectores or Apps). Some clients require you to first turn on a or to have administrator permissions.
Add a remote connector with the endpoint URL
Choose to add a and paste Eulerian's with appended (see Section 4).
Choose OAuth as authentication
Select as the authentication method. In many clients it's auto-detected from the URL; leave the Client ID/Secret blank unless Eulerian tells you otherwise.
Sign in to Eulerian
The client redirects you to Eulerian's sign-in screen. Enter your Eulerian username and password. You paste no token here: the client never sees your password.
Authorize access (Approve)
Eulerian shows the requested permissions (for example eulerian:reports.read). Review them and click to authorize (or "Deny" to cancel).
Example of Eulerian's authorization screen; the client name and permissions may vary.
Always review the permissions before approving. For read-only reports, eulerian:reports.read is enough; grant write permissions only if your use case requires it.
Enable it and use it
The connector is now connected. Some clients also require you to (in the tools menu). Then ask in natural language, for example:
Which Eulerian tools do you have access to?
Nothing installed and no tokens pasted. You can revoke access at any time from your client or from your Eulerian account.
Eulerian's part is always the same; this is just a map of where each platform adds the connector. For the illustrated detail, see the specific guide for each client:
- Settings → Connectors → "Add custom connector".
- manual method or one-click .dxt extension.
- Settings → Apps → Advanced settings → Developer mode → "Create app".
- in the Gemini console/admin, depending on the edition (verify).
- create it in Mistral Studio → Connectors; then enable it in each conversation.
- (Codex, VS Code + Copilot, Mistral Vibe CLI, Gemini CLI): configured via a configuration file; see each one's guide.
No token is stored on your computer or in the browser. You authenticate with your Eulerian account and Eulerian grants the client a limited access that is revocable at any time.
Review the permissions on Eulerian's authorization screen before clicking "Approve" and grant only what's needed. Avoid write permissions if you won't use them.
Only add MCP servers from developers you trust. Always verify the origin of the URL: here, the developer is Eulerian.
The endpoint must respond over HTTPS with a valid TLS certificate and be reachable over the internet, since the connection leaves the AI provider's servers.
Before using real business data, confirm with IT which AI platforms are approved for processing company data.
Look for "Connectors" or "Apps" in the client's settings. Some require turning on a developer mode or administrator permissions (see Sections 3 and 6).
Check the URL: it must be your Eulerian API endpoint with /mcp appended, over HTTPS and with a valid TLS certificate.
The endpoint must be reachable over the internet: the connection leaves the AI provider's servers, not your computer. If it's behind a firewall or VPN, it won't connect.
Use your Eulerian credentials (not the AI client's). If you have access to several grids, use the endpoint with the correct parameter.
On Eulerian's authorization screen you must click "Approve" (not "Deny"). If you clicked "Deny", repeat the connection flow.
Some clients require enabling the connector in each conversation (tools menu). Enable it and ask again.