Hex MCP connector
The Hex connector brings Hex projects, notebook cells, runs, and threads into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person can search, build, and run analyses within their own Hex access, with every call logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Regions: US and EU. Elaichi supports all of them; you pick your region when you connect.
Find the Hex project that tracks weekly active users
Working in Hex with Elaichi
-
Search projects
-
Get thread
-
Get me
How to connect Hex to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
Hex MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Hex through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Hex is logged.
-
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”
What connecting Hex gets you
6 screens from Elaichi, each doing one job for your Hex account.
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, Cursor or Microsoft Copilot
The agent
Ask about your Hex projects in plain language.
Answers come from live Hex projects, cells, and run outputs, not a stale export.
Copy the endpoint
AI apps
Use Hex from Claude, ChatGPT, Cursor, Microsoft Copilot, or Microsoft Copilot.
One governed endpoint for the whole organization, with no SDK and no shared API key.
Tool catalog
18 Hex tools, ready without writing code.
Projects, cells, runs, threads, and data connections, covered the moment Hex is connected.
Toolboxes
Every team gets its own Hex toolbox.
Analysts run and edit notebooks while Finance reads outputs, each from a scoped toolbox.
Shared connections
Share one Hex connection, never the credential.
Teammates run notebooks through a shared connection without ever seeing the sign-in.
Audit log
Know who ran which Hex notebook, and when.
Every cell edit, run, and thread is logged with the person, time, and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
Hex
Queued
Workflows
Schedules run Hex work end to end.
Runs fetch, group, and draft from Hex notebooks, and a person approves before posting back.
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%
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.
Why connect Hex's MCP server through Elaichi
Hex builds and runs this MCP server. Elaichi sits in front of it, so Hex's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Hex's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Hex's tools at the same Elaichi address as every other connected app. Nobody adds Hex's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Hex sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Hex's server. By default, a tool Hex does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Hex
Hex builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Hex team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting cell deletion or edits. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot