- Integration Guide with Claude (web)
- For users without advanced technical knowledge
- Remote connector with OAuth · nothing to install · Claude.ai
This guide connects (or the desktop/mobile app) directly to Eulerian's . Authentication is handled via : you install nothing, use no terminal, edit no files, and . You just add a «custom connector» with a URL and sign in with your Eulerian account. The desktop method (separate guide) installs a local «bridge» with Python and stores your token in a file. The web method uses a remote endpoint + OAuth sign-in: there's nothing to install and Claude never sees your password. Both give access to the same data; pick whichever fits your case.
- Check last week's paid-search campaign performance with a single sentence.
- Find out 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.
You need these four things before continuing:
Custom connectors (remote MCP) are available on the Free, Pro, Max, Team and Enterprise plans. Free is limited to 1 connector; for professional use we recommend Pro or higher.
On Team and Enterprise plans, an Owner or Primary Owner must first add the connector at the organization level (Organization settings > Connectors). Afterwards, each user connects individually with their own Eulerian account.
Provided by Eulerian; it looks like https://your-instance.api.eulerian.com/mcp . It must be reachable over the public internet, because the connection originates from Anthropic's servers (not from your computer).
Your Eulerian username and password. You'll sign in during the OAuth step. Unlike the desktop method, there is NO API token to paste here.
This method needs no Python, no terminal and no configuration file. Everything is done from Claude's interface and the Eulerian sign-in screen.
In Claude.ai , open your settings menu and go to (under «Customize»). Click the / button and choose . A dialog like this opens: The «Add custom connector» dialog (BETA): a field for the name, one for the remote MCP server URL, and advanced OAuth options.
Enter a descriptive (for example «Eulerian») and, in , paste the URL Eulerian gave you. Leave and blank unless Eulerian tells you otherwise.
Example with Eulerian's remote MCP server name and URL filled in (the values shown are for demonstration).
Claude reminds you to add connectors only from developers you trust: Anthropic does not control the tools a third-party connector exposes. In this case, the developer is Eulerian.
When you click , the connector is created but not yet connected; you'll see . Click to start the secure connection.
The newly created connector, not connected yet. Click «Connect» to start the OAuth flow.
Eulerian's sign-in page opens. Enter your Eulerian and and click (Sign in).
Eulerian's sign-in screen during the OAuth flow (username hidden for privacy).
You authenticate with your own Eulerian account via OAuth 2.1. Claude never sees your password: Eulerian grants it only a limited, revocable access.
Eulerian shows which permissions Claude is requesting — for example (read reports). Review them and click to authorize (or «Deny» to cancel).
Eulerian's authorization screen: Claude requests the eulerian:reports.read permission. Click «Approve».
The connector is now . In a conversation, click the button (bottom-left) → and enable the Eulerian connector for that conversation. Then ask in plain language, for example:
Which Eulerian tools do you have access to?
Nothing installed and no tokens pasted. You can enable or disable the connector per conversation from the «+» button → Connectors.
If your account is part of an organization (Team or Enterprise), members add the connector on their own. First, an or must add it at the organization level:
- Go to and add the custom connector with Eulerian's URL.
- Once added, each member connects individually by following steps 3 to 5 above, .
This way, Claude only accesses the data each user can see in Eulerian. There is also a beta option for to authorize the connector once for the whole team.
Because authentication uses and is offloaded to the MCP client, the same Eulerian remote endpoint should work with other MCP-capable web clients.
The Eulerian side (endpoint URL + OAuth sign-in + authorization) is always the same. What changes is where each platform adds the connector. See Eulerian's OAuth 2.1 documentation for the details.
With the web connector, no token is stored in the browser or on your computer. You authenticate with your Eulerian account and Eulerian grants Claude a access (for example, read-only on reports) that is at any time.
Always review the permissions requested on the authorization screen (for example eulerian:reports.read) before clicking «Approve». Grant only what's necessary.
Add only connectors from developers you trust. A connector can read and act on data, so always verify where the URL comes from.
Before using real business data, confirm with IT which AI platforms are approved. On Team/Enterprise, centralized connector management makes this easier.
Check that your plan allows custom connectors. On Team/Enterprise, an Owner/Primary Owner must first add the connector at the organization level (see Section 4).
Allow browser pop-ups for claude.ai and try again. Also check that the endpoint URL is exactly the one Eulerian gave you. The endpoint must be reachable over the public internet: the connection originates from Anthropic's servers, not from your computer. If the server is behind a firewall or VPN, it won't connect.
Use your Eulerian credentials (not your Claude ones). If you have access to several grids, use the URL with the correct parameter Eulerian indicated.
On Eulerian's authorization screen you must click «Approve» (not «Deny»). If you clicked «Deny», repeat step 3 (Connect).
Enable it in the conversation via the «+» button (bottom-left) → Connectors.