BI
Hex MCP connector
The Hex connector brings Hex projects, notebook cells, runs, and threads into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can search, build, and run analyses within their own Hex access, with every call 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 to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Hex once
-
Open Connections, choose Add connection, and pick Hex.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Hex. Hex'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 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 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 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 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 through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Data
Find the project that already answers it
Search Hex projects by topic before anyone builds a new notebook, and open the one the team already trusts.
-
Analytics
Build a notebook from a plain question
Create a Hex project, add SQL and chart cells, run them, and pull the output back into the conversation.
-
Finance
Rerun the month-end notebook and read it
Kick off the month-end Hex notebook, wait for the run to finish, and get the cell outputs and chart images without opening a browser.
-
Product
Ask a follow-up in a Hex thread
Start a thread against a Hex project, keep the conversation going, and get answers grounded in the project's own data connections.
-
Marketing
Fix a cell after the campaign changes
Update the query in a Hex cell when a campaign name or date range changes, run it, and check the new output.
-
Operations
See which data connections are available
List the data connections set up in Hex so a request lands on the right warehouse before a notebook is built.
Try asking
- “Find the Hex project that tracks weekly active users”
- “Rerun the revenue notebook and show me the final chart”
- “Add a cell that splits churn by plan and run it”
Compare
Elaichi vs Zapier MCP vs Composio for Hex
All three can connect Hex 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 tools | Allow or restrict single Hex 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 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 tools for your AI agents
18 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hex, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Hex builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Hex gets you
6 screens from the product, each doing one job for your Hex account.
The agent
Ask about your Hex projects in plain language.
Answers come from live Hex projects, cells, and run outputs, not a stale export.
- projects
- cells
- runs
- threads
Ask Elaichi to work across your apps.
Find the Hex project that tracks weekly active users
Rerun the revenue notebook and show me the final chart
Add a cell that splits churn by plan and run it
Also runs in Claude, ChatGPT or Cursor
MCP clients
Use Hex from Claude, ChatGPT, or Cursor.
One governed endpoint for the whole organization, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
18 Hex tools, ready without writing code.
Projects, cells, runs, threads, and data connections, covered the moment Hex is connected.
- Search projects
- Create thread
- Get thread
- Continue thread
Toolboxes
Every team gets its own Hex toolbox.
Analysts run and edit notebooks while Finance reads outputs, each from a scoped toolbox.
- Data
- Analytics
- Finance
- Product
Shared connections
Share one Hex connection, never the credential.
Teammates run notebooks through a shared connection without ever seeing the sign-in.
- Data platform
- Analytics
- Finance
- Product
Audit log
Know who ran which Hex notebook, and when.
Every cell edit, run, and thread is logged with the person, time, and resource.
- 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 work end to end.
Runs fetch, group, and draft from Hex notebooks, and a person approves before posting back.
Hex digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch projects
Hex
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
Queued
Collections and dashboards
Hex health numbers, computed with no model.
Four metrics, 14 days of projects created, and a breakdown by team, refreshed on schedule.
Hex 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 platform 34%
Analytics 27%
Finance 21%
Product 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Hex to Claude?
Connect Hex in Elaichi first, where you sign in to Hex over OAuth in your browser and approve access, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Hex projects are available in the conversation.
Does Hex work with ChatGPT and Cursor as well as Claude?
Yes. Hex is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. There is nothing to set up separately for each one.
What can an AI agent actually do with my Hex data?
With Hex connected, an agent can search your projects, open one, read its cells, add or change a cell, run a cell or the whole notebook, and bring back the output or a chart image. It can also start a thread in Hex, ask a follow-up, and tell you which data connections are available. Short, concrete asks work best, such as rerun the churn notebook and show me the final chart.
Does connecting Hex give the AI access to every project in the workspace?
No. Every call runs as the person who signed in to Hex, so the agent sees only the projects, cells, and data connections that person can already open in Hex. Elaichi can narrow that further with restrictions, but it can never grant anything Hex itself has not granted.
Can I stop an agent from deleting or changing things in Hex?
Yes. Restrictions in Elaichi apply per action, so you can allow searching and running Hex notebooks while blocking cell deletion or edits. A restricted action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it.
What happens to a Hex connection when someone leaves?
Offboarding that person in Elaichi ends their access to Hex through every client at once. A Hex connection they shared keeps working for everyone else on the team. Disconnecting Hex once in Elaichi removes it from Claude, ChatGPT, Cursor, and the Elaichi Agent together.
Does the Hex MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Hex 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?
Yes. Both let Claude, ChatGPT or Cursor use Hex. 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 call.
How is Elaichi different from Composio for Hex?
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: 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 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.