> ## Documentation Index > Fetch the complete documentation index at: https://docs.rippit.com/llms.txt > Use this file to discover all available pages before exploring further. # Hex > Let the Rippit agent ask questions of your data through Hex Threads and work in Hex projects. Connect Hex when the answer to a question about your conversations lives in the warehouse, and your analysts already answer those questions in Hex. The Rippit agent can find the relevant Hex project, start a Thread that asks Hex's own agent to analyze the data, and read the result back, so a question like "did refund tickets rise with the pricing change?" can pull the pricing numbers rather than guess at them. ## What the agent gets * **Project search**, to find the notebook or app that already answers a question. * **Threads**: start a Hex Thread with a question, read its answer and charts, and continue it with follow-ups. Hex's agent picks the data connection and writes the analysis. * **Project editing**, if the connecting user is a Hex Editor and you enable the write tools: read and change cells in a project's draft, run cells or the whole notebook, and read outputs. Threads created through Rippit behave exactly like Threads started in the Hex app and appear there. ## Your tool list depends on the connecting user's Hex role Hex exposes tools by role. A user with Hex's **Explorer** role sees the five knowledge tools: project search, the three Thread tools, and `get_me`. A user with the **Editor** role also sees the project editing tools, which is where every write tool lives. A connection authorized by an Explorer will never show the editing tools, however Rippit's tool selection is set. After connecting, **Manage tools** on the connection card shows what your connection actually exposes. ## Setup Nothing to configure in Hex. Rippit registers itself as an OAuth client automatically, so a Full Admin only supplies the URL and signs in. Hex's MCP server is available on Team and Enterprise plans. 1. Find your Hex MCP server URL. It depends on where your workspace is hosted: | Hosting | URL | | --------------------------------- | ------------------------------------- | | US multi-tenant (most workspaces) | `https://app.hex.tech/mcp` | | EU multi-tenant | `https://eu.hex.tech/mcp` | | HIPAA multi-tenant | `https://hc.hex.tech/mcp` | | Single-tenant | `https://.hex.tech/mcp` | 2. In Rippit, go to **Connections → MCP Servers**, choose **Hex**, and paste the URL. Rippit checks that it points at a `hex.tech` host. 3. Click connect and sign in to Hex. Hex's own guide is at [Hex MCP server](https://learn.hex.tech/docs/api-integrations/mcp-server). ## Identity and scope Hex's MCP server acts as the person who authorized it. Workspace and project permissions apply as they would in the Hex app: a project not shared with the connecting user is not searchable or editable through Rippit, and Hex admins cannot bypass project sharing through MCP either. Data connections a Hex admin has marked sensitive are excluded from MCP entirely. MCP access is separate from Hex's workspace API access setting, so turning API access off in Hex does not turn this connection off. An organization-wide connection shares the connecting user's Hex access with everyone using the agent. Authorize with an account whose project access you are comfortable extending that far. Hex has no application-level token for its MCP server, so connecting as a service account is not an option. The **scope** you choose at setup decides whether Agent Apps can use the connection, exactly as with every other connector. ## Tools The read set is enabled by default; write tools stay off until a Rippit Full Admin enables them under **Manage tools**. Tools marked Editor only appear when the connecting user has that Hex role. | Tool | Access | Hex role | What it does | | ----------------------- | ------ | -------- | ----------------------------------------------------------------------- | | `search_projects` | Read | Explorer | Search the workspace's projects | | `create_thread` | Write | Explorer | Start a Thread that asks Hex's agent a question about your data | | `get_thread` | Read | Explorer | Read a Thread's messages and results, waiting if it is still running | | `continue_thread` | Write | Explorer | Add a follow-up message to an idle Thread | | `get_me` | Read | Explorer | The connected user and workspace | | `get_project` | Read | Editor | Read a project's metadata | | `create_project` | Write | Editor | Create a project | | `list_cells` | Read | Editor | List the cells in a project's draft, with their code, SQL, and markdown | | `get_cell` | Read | Editor | Read one cell | | `get_cell_output` | Read | Editor | Read the latest output of a SQL cell in the draft | | `create_cell` | Write | Editor | Add a cell to a project's draft | | `update_cell` | Write | Editor | Change a cell's source or data connection | | `delete_cell` | Write | Editor | Delete a cell from the draft | | `run_cell` | Write | Editor | Run a cell and what it depends on | | `run_notebook` | Write | Editor | Run the whole draft notebook | | `get_run` | Read | Editor | Check a project run's status | | `list_data_connections` | Read | Editor | List the workspace's data connections, to pick one for a SQL cell | Starting or continuing a Thread counts as a write because it creates content in Hex and consumes Hex's agent usage, even though it changes no existing project.