Specification feature · interfaces

MCP progress notificationsMCP 2026-07-28

Receive progress updates for long-running requests.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP progress notifications: 1 supported, 0 partial, 0 unsupported, 30 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP progress notifications?

Read across for the answer. 1 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

  • Supported1
  • Partial0
  • Unsupported0
  • Unknown30
  • Not applicable0

Web

9 products

Desktop

13 products

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Receive progress updates for long-running requests.

This row remains unknown for a product until exact, dated evidence covers this capability rather than MCP generally.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Copilot Chatdesktop · current
Supported
Target
VS Code source commit a39698f7 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • protocol-revisionthe inspected implementation declares MCP 2025-11-25; exact 2026-07-28 revision negotiation is tracked separately
Evidence
  1. 1. VS Code source exposes and fires an event for MCP notifications/progress messages.