Hatchet MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HATCHET_CLIENT_TOKEN | Yes | Your Hatchet client token |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workflowsA | List all registered Hatchet workflows. Returns a list of workflows with their IDs, names, and descriptions. |
| list_runsA | List workflow runs with optional filters. Args: workflow_name: Filter by workflow name (e.g., 'qa-workflow', 'embed-workflow') status: Filter by status ('queued', 'running', 'completed', 'failed', 'cancelled') since_hours: How many hours back to search (default: 24) limit: Maximum number of runs to return (default: 50) Returns a list of runs with their status, metadata, and timing info. |
| get_run_statusB | Get the current status of a specific workflow run. Args: run_id: The ID of the workflow run Returns the run's current status and details. |
| get_run_resultB | Get the result/output of a completed workflow run. Args: run_id: The ID of the workflow run Returns the run's output data if completed, or current status if still running. |
| get_queue_metricsA | Get queue depth and job counts by status. Args: workflow_name: Optional workflow name to filter metrics Returns counts of jobs in each status (queued, running, completed, failed). |
| search_runsA | Search runs by metadata key-value pairs. Common metadata keys:
Args: metadata_key: The metadata key to search (e.g., 'audit_id') metadata_value: The value to match status: Optional status filter since_hours: How many hours back to search (default: 24) limit: Maximum runs to return (default: 50) Returns matching runs with their full metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GJakobi/hatchet-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server