# 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.

Source: https://elaichi.ai/connectors/hex/

## Facts

| | |
| --- | --- |
| Application | Hex |
| Category | BI |
| AI tools | 18 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Hex builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@hex.tech |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Hex is connected

- 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

## Connect Hex in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Hex.
2. Optionally set Share with, then press Connect.
3. Approve it in Hex. Hex's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Hex tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hex MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Hex to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Hex tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Hex through Elaichi

### Find the project that already answers it

Data. Search Hex projects by topic before anyone builds a new notebook, and open the one the team already trusts.

### Build a notebook from a plain question

Analytics. Create a Hex project, add SQL and chart cells, run them, and pull the output back into the conversation.

### Rerun the month-end notebook and read it

Finance. 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.

### Ask a follow-up in a Hex thread

Product. Start a thread against a Hex project, keep the conversation going, and get answers grounded in the project's own data connections.

### Fix a cell after the campaign changes

Marketing. Update the query in a Hex cell when a campaign name or date range changes, run it, and check the new output.

### See which data connections are available

Operations. List the data connections set up in Hex so a request lands on the right warehouse before a notebook is built.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Hex connection?

Yes. One person connects Hex in Elaichi and shares the connection with a team, and nobody else handles a credential. Each teammate still signs in as themselves, so every run and edit in the audit log carries their own name.

### 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.

## All 18 Hex tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hex is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Search projects** (Search). Search for projects in your workspace. Returns both published and unpublished Hex projects (projectId, title, description, generated_summary, url, type).
- **Create thread** (Create). Create a new Hex Thread to ask questions about your data using the Hex Agent.
- **Get thread** (Get). Retrieve messages and results from an existing Hex Thread.
- **Continue thread** (Action). Continue a conversation by providing a new prompt to an existing Hex Thread.
- **Get me** (Get). Return the authenticated user and workspace. Useful for confirming which workspace an agent is connected to, and which role it is operating under.
- **Create project** (Create). Create a new, empty project in the workspace.
- **Get project** (Get). Retrieve metadata about a single project.
- **List cells** (List). List the cells in a project's draft version.
- **Get cell** (Get). Retrieve a single cell.
- **Create cell** (Create). Add a cell to a project's draft version.
- **Update cell** (Update). Update a cell's source. For SQL cells, you can also update the output dataframe name and the data connection.
- **Delete cell** (Delete). Remove a cell from a project's draft version.
- **Run cell** (Run). Run a single cell and its upstream dependencies in the draft version. The run is asynchronous.
- **Run notebook** (Run). Run the entire draft version of a project. The run is asynchronous.
- **Get run** (Get). Check the progress of a project run.
- **Get cell output** (Get). Read the latest output preview for a SQL cell in the active draft notebook session.
- **Get cell image** (Get). Retrieve a rendered PNG image of a chart cell.
- **List data connections** (List). List the workspace's data connections, so an agent can resolve a connection by name before creating or updating a SQL cell.