Claude Hex connectorWhat Claude can do in your Hex account.
The Claude Hex connector exposes 4 tools. 2 read your Hex workspace, 2 start or extend an analysis there, and 0 are left undocumented. Here is what Claude can find, what the Hex agent works out for you, and what a Hex admin keeps locked.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Hex connector changes for analysis
You have a numbers question and the data lives in Hex. Instead of opening a notebook, you ask Claude. It either surfaces a project that already answers it or hands the question to the Hex agent, which runs the analysis in your workspace. The connector keeps you posted on its progress in the chat.
Reuse work that already exists. Before you rebuild a churn chart, search_projects scans your Hex workspace, and Claude shows project cards with a title, a description and a direct link.
Ask for an analysis in plain English. Say you want weekly signups by acquisition channel: create_thread opens a Thread, Hex's analysis conversation. The agent's thinking steps and chart carousels then show up in the chat as widgets.
Drill down without starting over. A follow-up question extends the same Thread through continue_thread, while get_thread brings back messages and results.
What Claude does not do here: it does not create or edit Hex projects, because the notebook editing tools Hex describes are not on the directory sheet. It also skips connections flagged as sensitive unless a Hex admin allows them. And nothing kicks off by itself: no Thread starts when a table refreshes. That kind of hands-off chain is the job of an automation tool, a different trade; the Integrations hub covers that side. For a connector built around spreadsheet-style bases, see the Claude airtable connector.
Terms to know first
Five words, and the rest of the page reads straight through.
- Connector
- The link you set up once between Claude and your Hex workspace, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude chooses which to call on its own, and the directory sheet lists each by name.
- Authorization
- Hex's own sign-in screen, where you give Claude the access it will use afterwards. Granted once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it finishes an action that would change your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on, which is what lets an assistant like Claude talk to an outside service such as Hex.
Connect Hex to Claude
- 01
Locate Hex in your settings
Open Claude's settings, go to Customize, then Connectors, and search for Hex. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization first, and each member then connects on their own.
- 02
Start the connection
Click Connect next to Hex and sign in through the window Hex opens itself. If you have access to more than one Hex workspace, pick the one that holds your working data.
- 03
Approve the authorization screen
Read Hex's authorization screen before you accept: it decides what the access covers, not Claude. If the link breaks later, use Disconnect and connect again; you can also withdraw access from your Hex account.
The 4 tools of the Claude Hex connector
Hex gives Claude 4 tools: 2 that read your account, 2 that change something in it.
Two lookup tools and two that put the Hex agent to work. Names stay exactly as Claude shows them.
- 2 read
- 2 write
What Claude reads (2)
2 toolsTwo tools that look at your Hex workspace without adding to it.
search_projects
Looks through your Hex workspace for projects matching a query. Claude presents the hits as cards with a title, a description and a link to open the project.
get_thread
Retrieves the messages and results of an existing Thread. While an analysis is still running, the connector calls this tool again on its own to track progress and keep you posted.
What Claude starts in Hex (2)
2 toolsTwo tools that open or extend a Thread in your workspace. No source describes a specific confirmation, so the general rule below applies.
create_thread
Approval: see the ruleCreates a new Thread in your Hex workspace from your question. The Hex agent then works on your data, and its thinking steps and chart carousels appear in the chat.
continue_thread
Approval: see the ruleAdds a follow-up question to a Thread that is already open. The agent keeps the context of the earlier analysis and extends that same thread of work inside Hex.
What Claude confirms with you
By default, Claude stops and asks before any action it takes on an account on your behalf. Here that mostly concerns opening or extending a Thread.
On a Team or Enterprise workspace, owners choose whether members can let some actions through without being asked again. They can also cap what a connector does for the whole organization, for example keep search open and close everything else, and that setting binds everyone. Claude works with your rights and nothing more: what you cannot reach in Hex yourself stays closed to it. The official read-versus-write label for each tool only shows up in the settings of a connected account.
Which Claude plans include Hex
None of the 819 sheets in the official directory lists plan availability. Connector by connector, that information is not published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members connect one by one. For Hex's current status on your account, look at its sheet in the official directory. Hex also limits its server to some of its own tiers, which is settled on the Hex side, not in Claude.
Where the Hex connector stops
A connector is not an automation. Claude calls these tools while it answers you, never on its own when your data moves.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's developer docs have a page on it, so the limits below come from Hex's documentation. The tool list is an observed floor, not a ceiling, since an admin can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic notes on every sheet that it does not choose a publisher's tools or vouch for how they behave. Hex also presents its server as a beta.
Need help connecting Hex to Claude?
A person reads every message.
