hex-mcp MCP server
A MCP server for Hex that implements the following tools:
list_hex_projects: Lists available Hex projectssearch_hex_projects: Search for Hex projects by patternget_hex_project: Get detailed information about a specific projectget_hex_run_status: Check the status of a project runget_hex_project_runs: Get the history of project runsrun_hex_project: Execute a Hex projectcancel_hex_run: Cancel a running project
Installation
Using uv is the recommended way to install hex-mcp:
uv add hex-mcp
Or using pip:
pip install hex-mcp
To confirm it's working, you can run:
hex-mcp --version
Configuration
Using the config command (recommended)
The easiest way to configure hex-mcp is by using the config command and passing your API key and API URL (optional and defaults to https://app.hex.tech/api/v1):
hex-mcp config --api-key "your_hex_api_key" --api-url "https://app.hex.tech/api/v1"
[!NOTE] This saves your configuration to a file in your home directory (e.g.
~/.hex-mcp/config.yml), making it available for all hex-mcp invocations.
Using environment variables
Alternatively, the Hex MCP server can be configured with environment variables:
HEX_API_KEY: Your Hex API keyHEX_API_URL: The Hex API base URL
When setting up environment variables for MCP servers they need to be either global for Cursor to pick them up or make use of uv's --env-file flag when invoking the server.
Using with Cursor
Cursor allows AI agents to interact with Hex via the MCP protocol. Follow these steps to set up and use hex-mcp with Cursor. You can create a .cursor/mcp.json file in your project root with the following content:
{
"mcpServers": {
"hex-mcp": {
"command": "uv",
"args": ["run", "hex-mcp", "run"]
}
}
}
Alternatively, you can use the hex-mcp command directly if it's in your PATH:
{
"mcpServers": {
"hex-mcp": {
"command": "hex-mcp",
"args": ["run"]
}
}
}
Once it's up and running, you can use it in Cursor by initiating a new AI (Agent) conversation and ask it to list or run a Hex project.
[!IMPORTANT] The MCP server and CLI is still in development and subject to breaking changes.
Metadata
Release files for hex-mcp 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hex_mcp-0.1.10.tar.gz | 17.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hex_mcp-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.5 kB
Release files / hex_mcp-0.1.10.tar.gz
| Download URL | hex_mcp-0.1.10.tar.gz |
|---|---|
| Size | 17.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a45649fa4745dd509ee3f3018bca20e6d46452e70566991dbebcab85a4f6d1eb
|
|
BLAKE2b-256 checksum How to use checksums |
d99eb9345342d0765fd00712899f140d754e55e62d994f169016851faef27673
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Release files / hex_mcp-0.1.10-py3-none-any.whl
| Download URL | hex_mcp-0.1.10-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42d9b12c631e645a530c916c2abde16b13da9d877ec4327a19ac5be0676b6499
|
|
BLAKE2b-256 checksum How to use checksums |
65196e042ac596d19f4f5e6625bccbc29f6cec391fb8bac0440cd50eaf57ac40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.3
|
Security for hex-mcp 0.1.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.