Task management for long-running MCP operations (experimental).

Tasks provide a durable state machine for operations that may take time to complete. Clients can poll for status, cancel in-flight operations, and receive results asynchronously.

Task Lifecycle

working → completed
working → failed
working → cancelled
working → input_required → working (after elicitation)

Usage

Tasks are stored in a pluggable store (defaults to ETS via ConduitMcp.Session.EtsStore pattern). The task registry is managed per-server.

Configuration

Enable tasks in your transport config:

{ConduitMcp.Transport.StreamableHTTP,
  server_module: MyServer,
  tasks: [enabled: true]}