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

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

## Facts

| | |
| --- | --- |
| Application | Hex (EU) |
| Category | BI |
| AI tools | 18 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Hex (EU) 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 (EU) is connected

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

## Connect Hex (EU) in Elaichi

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

1. Open Connections, choose Add connection, and pick Hex (EU).
2. Optionally set Share with, then press Connect.
3. Approve it in Hex (EU). Hex (EU)'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 (EU) tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hex (EU) 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 (EU) 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 (EU) 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 (EU) 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 (EU) 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 (EU) through Elaichi

### Build a notebook from a question

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

### Rerun the month-end notebook on demand

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

### Pull the chart from last week's campaign report

Marketing. Ask for the campaign chart and the agent finds the right Hex project, grabs the cell image, and drops it into your update.

### Continue an analysis thread where you left off

Product. Open a thread in Hex, ask a follow-up about activation or retention, and keep the conversation going without rebuilding the query.

### Find the pipeline analysis someone already built

Sales ops. Search Hex projects by topic, open the one that matches, and read the latest cell output instead of asking around in chat.

### Fix a broken cell and run it again

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

## 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. 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 (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](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 (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 my team share one Hex (EU) connection?

Yes. One person connects Hex (EU) in Elaichi and shares it with a team, and nobody else handles a token or credential. Each teammate still signs in to Elaichi as themselves, so every notebook run or cell change in Hex is logged under their own name.

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

## All 18 Hex (EU) tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hex (EU) 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.