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.
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.
- 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
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.
One command plus a key — uv add hex-mcp, then supply credentials