Integration · Hex
Collaborative analytics as MCP threads.
Hex is the AI analytics platform built around collaborative notebooks. The official MCP brings the Hex Agent into Claude Desktop, Claude Code, Cursor, and any MCP client.
Hex's first-party MCP server (beta launched October 2025) lets agents search Hex projects, create and continue analytical Threads, and run notebooks via natural language. OAuth handshake is cloud-side. Hex Agent works across the workspace, so the MCP can surface relevant existing analyses, not just create new ones. Pairs well with dbt MCP (lineage discovery) and BigQuery or Snowflake MCP (warehouse access).
What you can do via MCP
Example prompts the agent runs.
“Find Hex projects related to customer churn from the last quarter.”
Calls the project-search tool, returns projects matching the query with their last-modified date, the workspace owner, and a snippet showing the relevance match.
“Create a thread to explore why conversion dropped in EMEA last week.”
Creates a Hex Thread with the question, attaches the relevant data connections, returns the thread URL so the analyst can pick it up in the Hex UI.
“Continue the thread on Q4 retention; segment by enterprise vs SMB.”
Resumes the existing thread with the segmentation request, executes the analysis in the notebook, returns the new cells plus the chart output.
“Pull the cells from the recent revenue forecast notebook so I can review the SQL.”
Calls the cell-content tool on the named project, returns the SQL cells and the markdown narration so the analyst can audit the methodology without opening Hex.
“What data connections does our Hex workspace have access to?”
Returns the workspace's data connections (BigQuery, Snowflake, Postgres, etc.) with their access scope. Admins can restrict which connections are accessible from external integrations including the MCP.
Thread creation via the Hex MCP. The agent specifies the question; Hex creates the Thread; the analyst picks it up in the Hex UI.
# Hex MCP, called via the agent runtime
mcp.hex.create_thread({
workspace_url: "acme.hex.tech",
title: "EMEA conversion drop investigation",
question: "Why did conversion drop in EMEA last week? Segment by acquisition channel.",
data_connections: ["snowflake_prod_analytics"],
notify: ["analyst@acme.com"]
})
# Returns the thread URL plus the data connections attached.MCP integration
Hex MCP server.
- Server
- https://app.hex.tech/mcp (or your-company.hex.tech/mcp for single-tenant, EU, or HIPAA)
- Auth
- OAuth (handled by Hex)
- Hosting
- Hex hosted (Streamable HTTP)
- Scoping note
- Plan requirement: Explorer workspace role or higher. Admins can restrict which data connections are accessible from external integrations including the MCP.
- Project search across the workspace with relevance ranking
- Thread create and continue: agentic analysis the analyst picks up in Hex
- Cell content read: pull SQL or Python cells without opening the notebook
- Multi-data-connection access with the Hex Agent selecting the right warehouse for queries
- Pairs with dbt MCP for lineage discovery and BigQuery or Snowflake MCP for direct warehouse access
Visual demonstration
What this looks like in practice.
Q4 churn rate
3.2%
flatvs Q3Enterprise churn
1.1%
flatvs Q3SMB churn
5.8%
+1.2%vs Q3Threads opened
42
+18.5%vs Q3Threads resolved
38
+22.1%vs Q3Avg resolution time
2.4d
-8.2%vs Q3
- source
snowflake_prod_analytics
Snowflake
- source
bigquery_events_v2
BigQuery
- transform
Q4 churn investigation
thread
- transform
Revenue forecast 2026Q1
notebook
- exposure
Q4 board review
shared link
- exposure
Growth team dashboard
embed
CLI alternative
Hex REST API for non-MCP workflows.
Hex exposes a REST API for non-MCP workflows. For AI-driven analytics work the official MCP is the primary interface; the REST API fills in for embedding workflows, scheduled exports, and any operational integration the agent runtime is not the right place for.
Pairs with these skills
The PM data and analytics skill suite.
This integration pairs with the forthcoming data-warehouse-experimentation, feature-launch-playbook skills. The skill landing pages and SKILL.md sources land in subsequent dispatches; cross-link hyperlinks are added when the skill pages ship.