Skip to main content

Hex

Search Hex projects and run Hex's AI analyst on your data through the Hex MCP server.

Connect it with: MCP. Hex's own documentation: https://learn.hex.tech/docs/administration/mcp-server.

What agents can do​

Connect Hex so the agents working your tasks can reach it. With it connected, they can:

  • Search Hex projects and read a published app's results.
  • Ask Hex's AI to answer a data question against your workspace's connected warehouse (a connection marked sensitive needs Allow sensitive data connections in MCP, API, and CLI under Settings > Integrations).
  • Start a new Hex thread for an analysis and return the link in the task.

Before you start​

  • A Hex workspace on the Team or Enterprise plan, and a Hex user with the Explorer role or higher.
  • Your Hex address if it is not app.hex.tech (EU or single-tenant workspaces).
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Hex​

Hex's MCP server signs you in itself, so connecting needs no key and no app of your own.

  1. In Jaah, open Secrets and select New.
  2. Search for Hex and select its card.
  3. Name the secret and choose who can use it (see Who can use it).
  4. Fill in Server URL if your account is not on the default address (see below), and save.
  5. Select Connect Hex, sign in to Hex in the window that opens, and approve the access it lists.
  6. You land back in Jaah on the new secret. Then link it to the projects whose agents should use it (see Use it in an agent session).

Where to find it:

Connect with an API key​

Hex has no API key option in Jaah: connect with the sign-in above.

Use your own OAuth app​

Not needed: Hex's MCP server registers Jaah itself when you connect, so there is no app of your own to create.

Test the connection​

Select Test on the secret. Jaah makes one read-only call to Hex with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

Tell the agent in your task description which secret to use, for example “use the Hex secret org/hex”.

Hex also runs an MCP server, which gives agents ready-made Hex tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Hex secret, and confirm.
  3. New tasks on the project start with the Hex tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Reconnect: when Hex ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Hex's side too, revoke Jaah in Hex's settings.

Limitations​

  • Agents act as the signed-in Hex user and see only what that user can see.
  • Analyses run on your Hex plan and count toward its usage.
  • Agents can do only what the connected Hex account and its granted scopes allow.

Troubleshooting​

Test says Hex rejected the token (401)

The sign-in expired or was revoked. Select Reconnect and sign in to Hex again.

Test or Connect cannot reach the server

The Server URL is wrong for your workspace. Set it to the address you open Hex at followed by /mcp, then Reconnect.

The secret shows Needs reconnect

Hex ended the grant (a password change, a revoked connection or a long idle period). Select Reconnect on the secret and sign in to Hex again.

New tasks on the project have no Hex tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.

Still stuck? Select Test and read the result: it names the value Hex refused and the status it answered.

FAQ​

Does Jaah need an app registered at Hex?

No. Jaah registers itself with Hex's sign-in server the first time anyone connects, and every later connection reuses that registration.

Can I use Hex's EU or single-tenant cloud?

Yes. Set Server URL to that address followed by /mcp; Jaah dials it only after checking it resolves to a public address.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Hex account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.