Repository navigation
Conversation
Tool, resource and prompt registries are per-process Maps, while mcpBroadcastNotification with Redis reaches clients on every instance. A runtime registration announced with list_changed therefore sends clients on other instances to re-list against a registry that lacks it, and rolling redeploys briefly serve different lists. State that registration must be identical on every instance, at startup. Refs #237 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UF4S3w7iA83V9DVsasLJzM
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tool, resource and prompt registries are per-process
Maps, but with the Redis backendmcpBroadcastNotificationreaches clients on every instance. The README showed broadcastingnotifications/tools/list_changedby hand without saying that clients on other instances will re-list against a registry that does not have the change, or that lists differ during rolling redeploys.This adds a short "Tools, Resources and Prompts Across Instances" subsection under Redis / Multi-Instance Deployment, and a pointer next to the
list_changedbroadcast example:list_changedbroadcast is only safe on a single instance or when every instance performs the same registration;Docs only; lint and typecheck pass.
Refs #237
The design for automatic fleet-wide
list_changed(registry generations, redeploy signalling) remains open in #237 for after #170 lands.🤖 Generated with Claude Code
https://claude.ai/code/session_01UF4S3w7iA83V9DVsasLJzM