Claude Hebbia connectorWhat Claude can do in your Hebbia account.
The Claude Hebbia connector exposes 6 tools. 5 read, 0 write, 1 is described by no official source. Below: what Claude can pull from your firm's projects and sources, the admin switch that comes first, and what Hebbia keeps out of this release.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your deal team
You no longer switch to Hebbia to dig through a data room. With the connector on, Claude can see which organizations, projects and data sources you have in Hebbia, put a question to one project or to your firm's public sources, and bring back an answer with citations that point to the documents in Hebbia.
Interrogate one deal's documents. An analyst wants every change-of-control clause across a target's contracts. list_projects shows the projects holding private data you can reach, then ask_project runs the question strictly inside the chosen one and returns cited answers.
Check a market fact against your firm's sources. Before an investment committee, list_sources reveals which public data sources your organization has made available, and ask_sources queries them, picking sources on its own unless you name them.
Start in the right organization. If you belong to several, list_organizations comes first, since Hebbia says every other tool needs an organization identifier.
Now what the sheet leaves out. Hebbia calls this release read-only: no document upload, no project creation, no change to your data. It also documents matrix tools that the directory sheet read on October 1, 2026 does not list. And nothing runs on its own: no tool wakes up when a new document lands in a project. For that kind of background work, you want an automation tool, a different job; the Integrations hub covers that side.
The vocabulary in one minute
Five words you will meet while connecting Hebbia.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while answering you.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs by itself, and the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect Hebbia to Claude in three steps
- 01
Find Hebbia in Claude
In Claude's settings, open Customize, then Connectors, and look for Hebbia in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first, before each member can sign in on their side.
- 02
Start the connection
Click Connect on its row, then sign in to Hebbia in the window Hebbia opens itself. The access granted there is yours alone, given once per person. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before you accept. It belongs to Hebbia, not to Claude, and it decides what the access covers. You can also withdraw that access later from the Hebbia side.
The 6 tools, sorted by what they do
Hebbia gives Claude 6 tools: 5 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups: what Claude reads, and what no official source describes. Names stay as Claude shows them, in English.
- 5 read
- 1 not documented
What Claude reads (5)
5 toolsFive tools that browse or question your Hebbia content without changing it.
list_organizations
Returns the Hebbia organizations your login belongs to, with their names and identifiers. Hebbia tells Claude to start here when no organization is set, because every other tool expects one.
list_projects
Shows the projects holding private data that your account can open in the connected organization, each with a name, an identifier and a description.
list_sources
Brings up the public data sources your organization has opened to this connector, with names, identifiers and descriptions. Anything missing from that list cannot be queried through Claude.
ask_project
Puts a plain-language question to one project and keeps the search inside that project's data only. The reply arrives with inline citations and their full details, so you can trace each claim back to a document.
ask_sources
Queries your organization's public data sources in plain language. By default it selects the relevant sources itself; you can also hand it a precise list. Answers come back cited.
list_sources are reachable.Undocumented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and this page will not guess from a name.
ping
This name appears in the directory's tool list and that is all there is. Hebbia's documentation does not mention it and no Claude page does either, so this page says nothing more about it.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the conversation, when it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads open and closing writes, and nobody overrides that from their own account. Claude works with your rights and nothing more: a Hebbia project you cannot open stays closed to it, and only the sources your organization exposes are in reach.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer is published nowhere, connector by connector: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can connect. For the current state, check the connector's sheet in the official directory, the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a document is added to a project or a source refreshes.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Only Hebbia's own documentation covers this connector, and it describes adding Hebbia as a custom connector set up by a Claude admin.
Need help connecting Hebbia to Claude?
A person reads every message.
