Skip to content
AdminKit

Progress notification (MCP)

What is Progress notification (MCP)?

A progress notification is how the Model Context Protocol reports incremental status on a long-running request, sent as an optional notifications/progress message tied to a progressToken the client attached to its original request. AdminKit's MCP gateway sits in the request path where these notifications, along with the calls they describe, pass through.

By AdminKit team, Netbase JSC · Updated

A progress notification is how the Model Context Protocol reports incremental status on a request that may take a while to finish, such as a long-running tool call. A client that wants updates attaches a progressToken to its original request’s metadata; whichever side is handling that request then sends one or more notifications/progress messages carrying the same token along with a progress value and, optionally, a total, so the other side can show a percentage or step count instead of leaving the user staring at a frozen screen. Like all MCP notifications, these are plain JSON-RPC notifications — they carry no id and expect no reply — and sending them at all is optional for an implementation to support, so a client cannot assume it will receive one without checking first. The same token-based pattern appears in the Language Server Protocol, whose $/progress notification also carries a progress token, and which MCP’s specification cites as an inspiration.

Progress notifications are one of several optional notification-based utilities MCP defines, alongside cancellation and logging, each needing explicit client or server support to be useful.

AdminKit groups progress notification (MCP) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What identifies which request a progress notification belongs to?

The progressToken the client attached to its original request's metadata -- the notification carries the same token back so the client can match it up.

Is sending progress notifications mandatory for an MCP server?

No -- it's optional for an implementation to support, so a client can't assume it will receive one without checking the server's declared capabilities first.

What transport-level type are MCP progress notifications?

Plain JSON-RPC notifications -- they carry no id and expect no reply, the same as any other MCP notification.