LABSCO SUMMARY
Open-ended data questions answered by Hex's own analysis agent.
Teams already on Hex get their analysis agent and notebooks without switching tools: a Thread picks the data connection and returns charts and findings, and Editors can have notebook cells written and run.
What it is
A remote MCP server Hex runs at app.hex.tech/mcp, currently in beta. It connects your assistant to your own Hex workspace. Hex lists Claude, Cursor, ChatGPT, Codex and Glean among the clients it works with.
What you get
- Projects in your workspace found by search, published or not
- Data questions answered by a Hex Thread, Hex's analysis agent, with its charts and tables, and follow-up questions on the same Thread
- New projects created, and SQL, Python and Markdown cells added, edited and removed
- A single cell or the whole notebook run, with the run's status and a SQL cell's results
- A chart cell returned as an image
- Your workspace's data connections listed by name
Requirements
- A Hex workspace on the Team or Enterprise plan, and you sign in to it with OAuth.
- The Explorer role lets you search and ask questions; building and editing notebooks needs the Editor role and edit access to that project.
- Workspaces on their own address, such as eu.hex.tech, use that address in place of app.hex.tech.
- A Thread usually returns its findings within several minutes.
- Edits land straight in the project's draft, which collaborators see right away, so publish from Hex only once you have checked them.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen