How MCP tools report progress to agents via notifications
11/03/2026 — 11/03, 13:18·1 sources (all)·1 reports (all)
Key takeaways
- A tutorial explains that long-running MCP tools need progress reporting so agents can tell whether a tool is working, stuck or should be aba…
- the token is optional and tools should still run without it.
Background & analysis
On 2026-11-03, the AI section of DEV Community published a tutorial explaining how MCP tools can report progress to an Agent instead of leaving it spinning. The piece opens with the problem: a long-running MCP tool that gives no feedback turns the Agent into a black box. The Agent cannot tell whether the tool is working, has stalled, or should be abandoned, and users staring at a spinner have no better information. The tutorial then walks through the solution the Model Context Protocol provides: progress notifications, which let the tool report incremental progress on the same channel while the call stays open. To use them, the caller passes a progress token along with the request, and the server uses that token to keep sending percentage-based updates or stage markers without ending the call. The client can surface these updates to the user, and the final result is returned separately from the progress notifications themselves. One important caveat the tutorial stresses is that the token is optional: if the client does not supply one, the tool should run normally and simply forgo progress reporting. That is the entire scope of the guidance as published, with no follow-up coverage or changes to the mechanism reported since.
AI-generated from 1 reports · updated 3 days ago
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 3 days ago
Reports on this story headlines open the original
A long-running MCP tool that reports no progress turns the agent into a black box: it cannot tell whether the tool is working, stalled or worth abandoning. The Model Context Protocol defines progress notifications for this, where the caller supplies a progress token and the server emits percentage or stage updates on the same channel while keeping the final result separate. The token is optional, so the tool must still run when the client does not send one.
DEV Community · AIAI score 52
Other stories people are talking about
- Heat index 85NewDeveloper recounts why agents ignored his MCP tool1 sources
- Heat index 840OpenAI ships Images 2.6 with GIF and SVG output15 sources
- Heat index 675OpenAI says its cyber model pipeline confirmed 1,724 Linux kernel flaws and generated 948 privilege-escalation exploits11 sources
- Heat index 642RisingOpenAI GPT-5.6 Brings Major Agentic and Computer Use Upgrades13 sources
- Heat index 633RisingCat Wu, product lead for Claude Code, joins OpenAI9 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion

