rfd: add dynamic MCP server updates in live sessions#582
Open
OmChillure wants to merge 1 commit intoagentclientprotocol:mainfrom
Open
rfd: add dynamic MCP server updates in live sessions#582OmChillure wants to merge 1 commit intoagentclientprotocol:mainfrom
OmChillure wants to merge 1 commit intoagentclientprotocol:mainfrom
Conversation
benbrandt
reviewed
Mar 5, 2026
|
|
||
| ## What we propose to do about it | ||
|
|
||
| We propose adding a new `session/update_servers` request type, sent by the ACP Client to the Agent during an active session. The request carries the full updated list of MCP servers, which replaces the prior list entirely. The Agent connects to any newly added servers and disconnects from any that are no longer present. |
Member
There was a problem hiding this comment.
@ignatov I think in some ways this is tied to your intiative to clarify MCP lifecycle in general. i.e should it replace all?
Should we instead have a add/remove endpoint?
And a way to retrieve all currently configured MCPs in case there were some from other agent config?
|
|
||
| ## Elevator pitch | ||
|
|
||
| We propose adding a new `session/update_servers` request that allows ACP Clients to send a replacement list of MCP servers to an Agent during an active session — without requiring a session restart. This unblocks a class of client UX where users can add, remove, or reconfigure MCP servers mid-conversation and have the change take effect immediately. |
Member
There was a problem hiding this comment.
nitpick, I feel like this should be session/update_mcp_servers to be clearer what we are updating
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
2 participants
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.
Description:
This PR introduces an RFD for adding a new session/update_servers request to the Agent Client Protocol.
Motivation: Currently, MCP servers can only be provided during session setup (session/new, session/load, etc.). Once a session is established, its list of MCP servers is fixed. This forces users to restart their sessions (losing valuable context and history) just to add, remove, or reconfigure an MCP server.
Proposed Changes:
Introduce a session/update_servers request sent by the Client to the Agent.
The request payload contains the full replacement list of MCP servers (reusing the existing
McpServer
schemas).
The Agent gracefully connects to newly introduced servers and disconnects from those removed from the list.
Impact: This allows clients to confidently provide live MCP server management UIs. Settings changes to MCP configurations can instantly propagate to active agent sessions without interrupting the user's workflow.
Based on the feature request in discussion #556.