Skip to main content
Glama
Hatchet MCP Server

Hatchet MCP Server

by GJakobi

Hatchet MCP Server

MCP server for debugging and monitoring Hatchet jobs from Claude Code or other MCP clients.

Installation

git clone https://github.com/GJakobi/hatchet-mcp.git
cd hatchet-mcp
uv sync

Related MCP server: hatchet-mcp

Configuration

Add to your .mcp.json (Claude Code) or MCP client config:

{
  "mcpServers": {
    "hatchet": {
      "type": "stdio",
      "command": "uv",
      "args": ["run", "--directory", "/path/to/hatchet-mcp", "python", "-m", "hatchet_mcp.server"],
      "env": {
        "HATCHET_CLIENT_TOKEN": "your-hatchet-token"
      }
    }
  }
}

Available Tools

Tool

Description

list_workflows

List all registered Hatchet workflows

list_runs

List workflow runs with filters (workflow_name, status, since_hours, limit)

get_run_status

Get status of a specific run by ID

get_run_result

Get the output/result of a completed run

get_queue_metrics

Get job counts by status (queued, running, completed, failed)

search_runs

Search runs by metadata (e.g., audit_id, patient_id)

Example Usage

Once configured in Claude Code:

> List all Hatchet workflows
Uses: mcp__hatchet__list_workflows

> Show me runs that failed in the last 24 hours
Uses: mcp__hatchet__list_runs with status="failed"

> Find all runs for audit_id abc123
Uses: mcp__hatchet__search_runs with metadata_key="audit_id", metadata_value="abc123"

> What's the current queue depth?
Uses: mcp__hatchet__get_queue_metrics

Status Values

  • queued - Waiting to be processed

  • running - Currently executing

  • completed - Finished successfully

  • failed - Finished with error

  • cancelled - Manually cancelled

License

MIT

Available Tools

6 tools
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).

Inputs: workflow_name.

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.

Inputs: run_id (required).

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.

Inputs: run_id (required).

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.

Inputs: workflow_name, status, since_hours, limit. Returns: result

list_workflowsA

List all registered Hatchet workflows.

Returns a list of workflows with their IDs, names, and descriptions.

Inputs: no named parameters. Returns: result

search_runsA

Search runs by metadata key-value pairs.

Common metadata keys:

  • audit_id: The audit being processed

  • audit_type: Type of audit (e.g., 'standard', 'express')

  • patient_id: Patient being processed

  • application_id: Application ID

  • rule_id: Rule being processed

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.

Inputs: metadata_key (required), metadata_value (required), status, since_hours, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes focused on different aspects of workflow management (metrics, runs, workflows), but get_run_result and get_run_status could potentially overlap in some use cases since both retrieve information about specific runs. The descriptions help clarify that get_run_result focuses on output data while get_run_status focuses on current status, but an agent might still need to carefully choose between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout: get_queue_metrics, get_run_result, get_run_status, list_runs, list_workflows, and search_runs. This consistency makes it easy for agents to understand and predict tool functionality.

    Tool Count5/5

    Six tools is an appropriate number for a workflow management server. This provides comprehensive coverage without being overwhelming. The tools cover metrics retrieval, run status checking, run listing/searching, and workflow listing - a well-scoped set that addresses the core needs of interacting with a workflow system.

    Completeness4/5

    The tool set provides strong read/search capabilities for workflows and runs, with good coverage for querying metrics, status, results, and metadata. Minor gaps exist in write operations (no tools for creating/triggering workflows or managing runs), but for a monitoring/query-focused server, the surface is reasonably complete for its apparent purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      F
      maintenance
      Enables comprehensive Datadog monitoring capabilities including CI/CD pipeline management, service logs analysis, metrics querying, monitor and SLO management, service definitions retrieval, and team management through Claude and other MCP clients.
      13
      20
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for Hatchet, the durable orchestration engine, enabling LLMs to inspect workflow definitions, runs, logs, and more, with optional mutating tools for triggering, canceling, and managing workflows.
      73 PyPI
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides Claude AI assistants with focused monitoring tools for n8n workflow execution analysis, including active workflow listing, execution history with KPIs, and detailed failure information.
      1
      MIT