Protocols
Saved & recent

MCP cancellation

Also called: notifications/cancelled, MCP request cancellation

Cancellation tells an MCP server that a client no longer wants an in-progress operation. In the inspected 2026-07-28 revision, the signal depends on the transport: stdio uses notifications/cancelled with the request ID, while Streamable HTTP uses closure of that request’s SSE response stream. The client should stop waiting after cancellation.

For example, a user abandoning a long search can release the stream carrying its results. Cancellation can race with completion, so it does not prove that work never happened or undo an action already performed. A server may be unable to stop some operations. Timeouts provide another reason to cancel, but applications still need separate rules for any side effects.

Read first
MCP transports
Related
MCP transports, Timeout, MCP tool invocation
Further reading
MCP — cancellation, revision 2026-07-28
stdio request 17 active notifications/cancelled · requestId 17 Streamable HTTP request 17 · SSE response stream close this response stream completion race operation completes time → cancellation arrives stop requested completed effects remain
Cancellation uses a request ID on stdio or a request-stream disconnect on HTTP, and can arrive after work has completed.

View in the full Protocols collection