Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix MCP `notifications/resources/updated` not handled per spec [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47823•Fetched 2026-04-15 06:41:18
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
webpatserwebpatser
Participants
webpatserwebpatser
Timeline (top)
labeled ×2subscribed ×1

Claude Code accepts but silently drops notifications/resources/updated from MCP servers. Per the MCP specification, clients should handle this notification when a subscribed resource changes.

Error Message

Server sends ResourceUpdatedNotification via stdio transport → client returns no error → notification is silently ignored. The AI session is never informed.

Root Cause

Claude Code accepts but silently drops notifications/resources/updated from MCP servers. Per the MCP specification, clients should handle this notification when a subscribed resource changes.

RAW_BUFFERClick to expand / collapse

Summary

Claude Code accepts but silently drops notifications/resources/updated from MCP servers. Per the MCP specification, clients should handle this notification when a subscribed resource changes.

Current behavior

Server sends ResourceUpdatedNotification via stdio transport → client returns no error → notification is silently ignored. The AI session is never informed.

Expected behavior (per MCP spec)

The client should process the notification and make the updated resource available to the AI session.

Environment

  • Claude Code: latest (CLI, macOS)
  • MCP transport: stdio

extent analysis

TL;DR

The client likely needs to implement handling for the notifications/resources/updated notification to process resource updates from the MCP server.

Guidance

  • Review the MCP specification to understand the requirements for handling notifications/resources/updated notifications.
  • Verify that the client is correctly parsing and processing the ResourceUpdatedNotification sent via stdio transport.
  • Check the client's implementation to ensure it is updating the resource and making it available to the AI session as expected.
  • Investigate the client's error handling to determine why no error is returned when the notification is silently ignored.

Example

No code snippet can be provided without more information about the client's implementation.

Notes

The solution may depend on the specific implementation details of the client and its handling of MCP notifications.

Recommendation

Apply workaround: Implement custom handling for notifications/resources/updated notifications in the client, as the current implementation does not seem to follow the MCP specification.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#authentication issue#prompt issue#agent setup#task chaining#parallel task

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING