Skip to content
FlowMCP v4

MCP Tasks

Normative language (MUST/SHOULD/MAY) follows the conventions defined in Conformance Language.

Status

Section titled “Status”

Deferred to v2.1.0. This section is a placeholder.

MCP Tasks enable long-running asynchronous operations (e.g. executing a Dune Analytics query that takes 30+ seconds). The MCP protocol defines a task lifecycle with creation, polling, completion, and cancellation.

Why Deferred

Section titled “Why Deferred”

FlowMCP schemas describe how to interact with external API async patterns (job submission, status polling, result retrieval). The MCP Tasks protocol defines how the MCP server itself exposes async operations to AI clients. These are two complementary layers that need careful alignment.

v2.1.0 will define:

  • Schema-level fields for declaring async routes
  • Mapping between external API status values and MCP Task states
  • Integration with the MCP Tasks protocol (tasks/get, tasks/result, tasks/cancel)

Reference

Section titled “Reference”

Reserved Fields

Section titled “Reserved Fields”

Schema authors MAY include an async field in route definitions for forward compatibility. In v2.0.0, this field is ignored by the runtime but preserved for future use.

Section titled “Related”