Data & Analytics · Hex + Claude
Hex MCP with Claude: Run Analytics Workflows in Plain English
The short answer
Claude works with Hex through the Model Context Protocol (MCP), a secure standard that lets Claude use software with permissions you control. Once connected, Claude can list projects, inspect workspace resources, trigger project runs and help track analytics workflows through natural language requests.
What is Hex?
Hex is a collaborative data workspace where teams write SQL, Python and R notebooks together. It is used by data analysts, data scientists and analytics engineers to build dashboards, data apps and data science workflows. Teams share their work in one place, so business questions, analysis and results stay connected rather than scattered across files and chats.
How Claude connects to Hex through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other software. It lets Claude securely read information from a tool and take actions in it. The organisation decides exactly what Claude is allowed to see and do.
Once Hex is connected, Claude can typically list the projects in a workspace, look into the resources it contains and trigger project runs. Someone can ask in plain English for the latest version of a report to be refreshed, or for an overview of which analyses exist on a topic, and Claude carries out the request through Hex.
Connection uses a Hex API key, so access is tied to a credential your team manages and can revoke. We set up least-privilege access, so Claude only reaches what it needs. Consequential actions can require human approval, and every interaction can be logged for review.
What you can automate
Refreshing reports before the weekly meeting
A operations manager asks Claude to trigger the latest run of the sales performance project in Hex before Monday's review. Claude confirms which project it is running, starts the run and reports back when the outputs are ready, saving the analyst a manual check each week.
Finding existing analysis before starting again
A marketing lead asks, in plain English, whether anyone has already analysed customer churn by region. Claude searches the workspace projects and resources, lists matching work and summarises what each one covers, so teams avoid duplicating effort.
Tracking the status of analytics workflows
A head of data wants a quick view of which scheduled analytics workflows ran, and which need attention. Claude reviews the relevant projects and gives a plain summary, helping leaders follow progress without opening every notebook.
Helping new team members navigate the workspace
A new data analyst asks where the official pricing analysis lives and which notebooks feed it. Claude inspects the workspace resources and explains the structure, shortening onboarding and reducing questions to senior colleagues.
Routing data questions to the right project
A finance controller sends a question about monthly margins. Claude identifies the most relevant Hex project, checks its resources and points the requester to the correct analysis or triggers a refresh if the data is stale.
An end-to-end workflow: Weekly sales review pack
TriggerEvery Friday morning, a request arrives in the team's chat asking for the week's sales review to be prepared.
Claude lists the projects in the Hex workspace and identifies the sales performance project.
Claude triggers a run of that project so figures reflect the latest data.
Once the run completes, Claude checks the key outputs and flags any unusual changes for a person to review.
Claude drafts a short summary and places it in the team's Microsoft 365 document library for the sales lead.
A manager approves the summary before it is shared with the wider leadership group through the CRM reporting channel.
OutcomeLeaders receive a current, reviewed sales summary each week without analysts rebuilding the same checks by hand, freeing time for deeper analysis.
How we set it up
Free automation audit
We review how your team uses Hex today and identify the workflows worth automating, such as refreshes, lookups and status checks.
Secure API key connection
We connect Claude to Hex using an API key that your team owns and manages, so access can be reviewed or revoked at any time.
Least-privilege access design
We set permissions so Claude can only list, inspect and run the projects that each workflow needs, and nothing more.
Workflow build and testing
We design the end-to-end process across Hex and your other systems, with approval steps for consequential actions, and test it against real past requests.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your analysts and business users on how to make requests and review results.
Who benefits
- Head of Data or Analytics
- Faster access to project status and refreshes, with a clear audit trail of what was run and when.
- Data analyst or scientist
- Less time on routine refreshes and status checks, and more time on modelling and insight.
- Business operations leader
- Plain-English access to current analysis without needing to learn the workspace.
- IT or security lead
- Controlled, revocable API key access with least-privilege permissions and logging.
Security and control
- Access uses a Hex API key that your team owns, can rotate and can revoke at any time.
- Least-privilege permissions limit Claude to the projects and actions each workflow needs.
- People approve consequential actions, such as triggering runs that feed external reports.
- Audit logs record requests, runs and outputs so every action can be reviewed.
- Data handling is tested against your own policies before launch.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host the solution in their chosen region and align it with local data protection requirements. In India, workflows are designed to meet the Digital Personal Data Protection Act, 2023. In the UAE and Saudi Arabia, we follow local data protection laws, and hosting region is chosen to meet your specific legal and contractual requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Hex MCP server do?
The Hex MCP server gives Claude a secure way to work with your Hex workspace. Typically it allows Claude to list projects, inspect workspace resources and trigger project runs, all through natural language requests. It acts as a controlled bridge, so Claude only uses the capabilities your team has allowed.
Is connecting Claude to Hex secure?
Security depends on how the connection is set up. We use an API key that your team owns and can revoke, apply least-privilege permissions and require approval for consequential actions. Audit logs record activity so it can be reviewed. We also test the setup against your own security policies before launch.
What can Claude do with Hex once connected?
Claude can typically list the projects in your workspace, look into the resources they contain and trigger runs so reports refresh. It can also help people find existing analysis and check on workflow status. The exact actions are set by the permissions you approve.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused setup for a few workflows often takes a few weeks, including the free automation audit, design, testing, launch and team training. We confirm a realistic timeline during the audit.
Which access or permissions are needed?
In general, a Hex API key with permissions matching the workflows you want is needed. Your Hex administrator decides which access to grant. We recommend the narrowest permissions that still support the workflow, and we will confirm exactly what is required during the audit.