[Agent Builder] add confirmation support for MCP server#247831
Draft
pgayvallet wants to merge 6 commits intoelastic:mainfrom
Draft
[Agent Builder] add confirmation support for MCP server#247831pgayvallet wants to merge 6 commits intoelastic:mainfrom
pgayvallet wants to merge 6 commits intoelastic:mainfrom
Conversation
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
pgayvallet
added
release_note:skip
Contributor
Author
|
/ci |
Contributor
💔 Build Failed
Failed CI StepsHistory
|
leemthompo
added
the
feature:agent-builder
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
4 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.
Summary
Fix https://github.com/elastic/search-team/issues/12274
GETandDELETEroute for server->client communication and session cleanupIssues and limitations
Stateful MCP capabilities aren't going to properly function with multi-node Kibana deployments (at least as long as we don't have sticky session management), because all requests of a given MCP sessions must be handled/routed to the same node, due to the stateful nature of keeping multiple channels / sockets open for bi-dir communications.
Technically with this PR, that means:
Demo
Screen.Recording.2026-01-06.at.08.02.05.mov