BI
Hex (EU) MCP connector
The Hex (EU) connector lets Claude, ChatGPT, Cursor and the Elaichi Agent search your Hex projects, run notebooks, read cell output and start analysis threads, with every call made as the signed-in person and logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Hex (EU) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Hex (EU) once
-
Open Connections, choose Add connection, and pick Hex (EU).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Hex (EU). Hex (EU)'s own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Hex (EU) MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Hex (EU) MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Hex (EU) MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Hex (EU) to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Hex (EU) through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Data
Build a notebook from a question
Describe the analysis you need, and the agent creates a Hex project, adds SQL and text cells, and runs them against the data connection you point it at.
-
Finance
Rerun the month-end notebook on demand
Ask for the latest numbers and the agent runs the month-end notebook in Hex, waits for the run to finish, and reads the output back to you.
-
Marketing
Pull the chart from last week's campaign report
Ask for the campaign chart and the agent finds the right Hex project, grabs the cell image, and drops it into your update.
-
Product
Continue an analysis thread where you left off
Open a thread in Hex, ask a follow-up about activation or retention, and keep the conversation going without rebuilding the query.
-
Sales ops
Find the pipeline analysis someone already built
Search Hex projects by topic, open the one that matches, and read the latest cell output instead of asking around in chat.
-
Operations
Fix a broken cell and run it again
Point the agent at the cell that errored, have it update the query, run that cell alone, and check the output before touching the rest.
Try asking
- “Find the churn analysis project and run the latest notebook.”
- “Show me the output of the revenue cell in the Q3 project.”
- “Start a thread asking why signups dropped last week.”
Compare
Elaichi vs Zapier MCP vs Composio for Hex (EU)
All three can connect Hex (EU) to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Hex (EU) tools | Allow or restrict single Hex (EU) tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Hex (EU) call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Hex (EU) tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hex (EU), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Hex (EU) builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Hex (EU) gets you
6 screens from the product, each doing one job for your Hex (EU) account.
The agent
Ask Hex (EU) a question, get live answers.
Search projects, run a notebook and read cell output without opening Hex (EU).
- projects
- cells
- threads
- runs
Ask Elaichi to work across your apps.
Find the churn analysis project and run the latest notebook.
Show me the output of the revenue cell in the Q3 project.
Start a thread asking why signups dropped last week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Hex (EU) to every client.
Claude, ChatGPT and Cursor reach Hex (EU) over OAuth, no SDK and no shared key.
Copy the endpoint
Tool catalog
18 Hex (EU) tools, ready with no code.
Projects, cells, threads, runs and data connections, covered without writing a line of code.
- Search projects
- Create thread
- Get thread
- Continue thread
Toolboxes
Every team gets its own Hex (EU) toolbox.
Finance runs notebooks, marketing reads charts, each team scoped to the work it does.
- Data
- Finance
- Marketing
- Product
Shared connections
Share Hex (EU) access, never a credential.
One person connects Hex (EU), teams work through it, nobody else sees a token.
- Data EU
- Finance
- Marketing
- Product analytics
Audit log
Every Hex (EU) call is logged by name.
See who ran which notebook, edited which cell and when, in one append-only log.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Schedules run Hex (EU) work end to end.
Projects are fetched, grouped and drafted into a digest, approved, then posted back to Hex (EU).
Hex (EU) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Hex (EU)
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Hex (EU)
Queued
Collections and dashboards
Hex (EU) health, computed without a model.
Projects created over 14 days, split by team, refreshed on a schedule you set.
Hex (EU) health
Refreshed 4 minutes ago · every 15 minutes · from the projects collection
Projects
1,284 ↓ 12%
Cells
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Projects created
Last 14 days
By team
Share of activity
Data EU 34%
Finance 27%
Marketing 21%
Product analytics 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Hex (EU) to Claude?
Connect Hex in EU inside Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Hex (EU) connects over OAuth, so the sign-in step is Hex's own login page for the EU region, where you approve access as yourself. There is no OAuth application to register and no client ID or secret to generate.
Does Hex (EU) work with ChatGPT and Cursor as well as Claude?
Yes. Once Hex (EU) is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Hex in EU once and every client sees it.
What can an AI agent actually do with my Hex (EU) data?
With Hex (EU) connected, an agent can search your projects, open a notebook and list its cells, add or edit a cell, run a single cell or the whole notebook, and read the output or chart it produced. It can also start or continue an analysis thread in Hex and check which data connections a project uses. Short, concrete asks work better than long sentences, so 'run the churn notebook and read me the first table' beats a paragraph.
Does connecting Hex (EU) give the AI every project in my workspace?
No. Everything runs inside the access of the person who signed in to Hex in EU, so an agent sees the projects and data connections that person can already open, and nothing more. Elaichi can narrow that further with restrictions, but it can never widen what Hex grants.
Can I stop an agent from deleting or changing cells in Hex (EU)?
Yes. Restrictions in Elaichi work per action, so you can allow searching projects and reading cell output in Hex (EU) while blocking deleting cells, editing cells, or creating projects. A restricted action is never advertised to the AI client at all, so no prompt can reach it.
What happens to a Hex (EU) connection when someone leaves?
Offboarding the person in Elaichi ends their access to Hex (EU) through every client at once. If they had shared their Hex connection, it keeps working for everyone else on the team. Disconnecting Hex in EU once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Hex (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hex (EU) is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Hex (EU)?
Yes. Both let Claude, ChatGPT or Cursor use Hex (EU). Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Hex (EU) call.
How is Elaichi different from Composio for Hex (EU)?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Hex (EU): one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Hex (EU) in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.