Skip to content

No client-suite scenarios for the tasks extension (io.modelcontextprotocol/tasks) #374

Description

@maxisbey

The server suite has 10 tasks-* scenarios, but the client suite has none. SEP-2663 places normative requirements on clients too — most importantly:

A client that has negotiated this extension MUST be prepared to handle either CallToolResult or CreateTaskResult in response to any supported request it issues.

plus the tasks/get polling flow (pollIntervalMs handling), issuing tasks/update / tasks/cancel, and the Mcp-Name: <taskId> routing header on tasks/* requests.

python-sdk is landing a client-side transparent polling driver (modelcontextprotocol/python-sdk#3005) and currently has no way to verify it against the harness — client conformance can't observe any of the above.

Suggested client-suite scenarios:

  • tasks-client-create-handling — the harness server task-augments a tools/call; the client must handle the CreateTaskResult and fetch the result via tasks/get.
  • tasks-client-poll-interval — the client honors pollIntervalMs between polls.
  • tasks-client-routing-headers — the client stamps Mcp-Name: <taskId> on tasks/* POSTs.
  • tasks-client-terminal-handlingfailed / cancelled tasks are surfaced rather than polled forever.

AI Disclaimer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions