Skip to main content
Glama
franccesco

Hex API MCP Server

by franccesco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HEX_API_KEYYesYour Hex API key for authentication
HEX_API_BASE_URLNoOptional custom API base URL for Hexhttps://api.hex.tech/api/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_hex_projectsC

List all available Hex projects that are in production.

Returns:
    JSON string with list of projects
search_hex_projectsA

Search for Hex projects using regex pattern matching on project titles.

Args:
    search_pattern: Regex pattern to search for in project titles
    limit: Maximum number of projects to return (default: 100)
    offset: Number of projects to skip for pagination (default: 0)

Returns:
    JSON string with matching projects
get_hex_projectB

Get details about a specific Hex project.

Args:
    project_id: The UUID of the Hex project

Returns:
    JSON string with project details
get_hex_run_statusB

Get the status of a project run.

Args:
    project_id: The UUID of the Hex project
    run_id: The UUID of the run

Returns:
    JSON string with run status details
get_hex_project_runsC

Get the runs for a specific project.

Args:
    project_id: The UUID of the Hex project
    limit: The number of runs to return
    offset: The number of runs to skip

Returns:
    JSON string with project runs
run_hex_projectC

Run a Hex project.

Args:
    project_id: The UUID of the Hex project to run
    input_params: Optional input parameters for the project
    update_published_results: Whether to update published results

Returns:
    JSON string with run details
cancel_hex_runB

Cancel a running project.

Args:
    project_id: The UUID of the Hex project
    run_id: The UUID of the run to cancel

Returns:
    Success message

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose targeting specific resources and actions: listing/searching projects, getting project details, managing runs (initiate, check status, cancel), and retrieving run lists. No overlap exists between tools like list_hex_projects (all production projects) and search_hex_projects (pattern-based search), or between run management tools.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with 'hex' prefix: list_hex_projects, search_hex_projects, get_hex_project, get_hex_project_runs, run_hex_project, get_hex_run_status, cancel_hex_run. The naming convention is perfectly uniform throughout the set.

Tool Count5/5

With 7 tools, this is well-scoped for a Hex project management server. The count covers core operations (list, search, get, run, monitor runs) without being excessive or insufficient. Each tool serves a clear purpose in the workflow.

Completeness5/5

The tool surface provides complete coverage for Hex project management: discovery (list/search), inspection (get project details), execution (run project with parameters), run monitoring (status, list runs), and control (cancel run). No obvious gaps exist for the stated domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources