fix: refresh tool and prompt caches after remote MCP server reconnect#2246
Merged
dgageot merged 1 commit intodocker:mainfrom Mar 25, 2026
Conversation
After a successful reconnect in watchConnection, eagerly call refreshToolCache so the runtime picks up the new server's tools and the toolsChangedHandler is invoked. Without this, the runtime kept using its stale copy of the tool list. Add TestRemoteReconnectRefreshesTools to verify that when a remote MCP server restarts with a different set of tools the Toolset returns the updated tools and notifies the handler. Extract startMCPServer and allocateAddr test helpers to reduce duplication across reconnect tests. Fixes docker#2244 Assisted-By: docker-agent
rumpl
approved these changes
Mar 25, 2026
trungutt
approved these changes
Mar 25, 2026
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
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.
After a remote MCP server restarts, the tool/prompt caches were invalidated but the runtime was never notified to re-fetch. This caused stale tools to be returned after reconnection.
Changes
pkg/tools/mcp/mcp.go: CallrefreshToolCacheandrefreshPromptCacheinwatchConnectionafter a successful restart so the runtime picks up the new server's tools/prompts.pkg/tools/mcp/reconnect_test.go: AddTestRemoteReconnectRefreshesToolswhich verifies that after a server restarts with different tools,Tools()returns the new set andtoolsChangedHandleris called. ExtractstartMCPServer/allocateAddrhelpers to reduce duplication.Fixes #2244