list_hex_projectsLABSCO SUMMARY
Hex, driven from whatever runs your schedule.
Hex is where the analysis lives; the pipeline that should start it usually lives somewhere else. This closes that gap — a run begins from your DAG, its status is checkable, a stuck one can be killed, and the SQL inside is readable for migration or audit.
What it is
An MCP server for Hex covering orchestration and monitoring of project runs, read access to cell content, and permission management — the operational side of Hex rather than the notebook-authoring side.
What you get
- Projects listed and searched across workspaces, with metadata — owner, last edited, description
- A project run triggered from outside Hex, from an Airflow DAG or a CI pipeline
- Run status checked and run history read, for auditing or for confirming a scheduled run finished
- A long-running or stuck execution cancelled
- Notebook structure and cell metadata listed, with SQL source from SQL cells and Python or R from CODE cells
- A cell updated
- User and group sharing on a project managed, including workspace-wide and public access
Requirements
A Hex workspace and API access to it. Know the ceiling before you plan around it: cell access covers SQL and CODE cells only — MARKDOWN, INPUT and visualization cells are not readable, cells cannot be created or deleted, notebook structure cannot be changed, and query results and charts are not available. It is built for orchestrating and auditing Hex, not for authoring or debugging notebooks inside it.
Setup effort
One command plus a key — uv add hex-mcp, then supply credentials
USE CASES
01
Kicking off an analysis from a pipeline
Trigger the project run from outside Hex and take the run back by ID.
02
Confirming last night's scheduled run finished
Read the project's run history and check the status of the one you care about.
03
Killing a run that has hung
Find it in the run history and cancel it before it eats the warehouse.
04
Finding a project in a workspace full of them
Search by name, then read the project's metadata to confirm owner and last edit.
05
Auditing the SQL that is actually running
List the cells and read the SQL and code source out of them.
06
Fixing who can see a project
Update user and group sharing, including workspace-wide and public access.
26 tools
Listed in project docs. Your client may show a different list.
search_hex_projectsget_hex_projectrun_hex_projectget_hex_run_statusget_hex_project_runscancel_hex_runlist_hex_cellsupdate_hex_cellupdate_hex_project_user_sharingupdate_hex_project_group_sharingupdate_hex_project_collection_sharingupdate_hex_project_workspace_sharinglist_hex_collectionsget_hex_collectioncreate_hex_collectionupdate_hex_collectionlist_hex_groupsget_hex_groupcreate_hex_groupupdate_hex_groupdelete_hex_grouplist_hex_data_connectionsget_hex_data_connectioncreate_hex_data_connectionupdate_hex_data_connectionBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- uv on PATH
- HEX_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uv add hex-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"hex-mcp": {
"command": "uv",
"args": [
"run",
"hex-mcp",
"run"
]
}
}
}The configuration on this page does not set HEX_API_KEY. The README's recommended way is hex-mcp config --api-key "your_hex_api_key", which saves it to ~/.hex-mcp/config.yml for every run. As an environment variable it has to be global for Cursor to pick it up, or loaded with uv's --env-file flag.
Cursor — binary on PATH
CURSOR — BINARY ON PATH · JSON
{
"mcpServers": {
"hex-mcp": {
"command": "hex-mcp",
"args": [
"run"
]
}
}
}The configuration on this page does not set HEX_API_KEY. The README's recommended way is hex-mcp config --api-key "your_hex_api_key", which saves it to ~/.hex-mcp/config.yml for every run. As an environment variable it has to be global for Cursor to pick it up, or loaded with uv's --env-file flag.
