add MCP Apps ACP surface and capability negotiation#8595
Closed
add MCP Apps ACP surface and capability negotiation#8595
Conversation
This was referenced Apr 16, 2026
Signed-off-by: Andrew Harvard <aharvard@squareup.com>
aharvard
force-pushed
the
feat/mcp-apps-capability-negotiation
branch
from
e12a0ec to
39eff42
Compare
Collaborator
Author
|
taking another route |
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.
This is PR 1 of 3 in a stacked PR sequence for MCP Apps in Goose2.
The full feature delivery depends on all three PRs merging. PR 2 stacks on this one, and PR 3 stacks on PR 2.
The overall goal of this work is to let Goose2 behave like a real MCP Apps host. This PR handles the backend negotiation layer that everything else depends on. It teaches Goose ACP how to understand Goose2's MCP Apps capability metadata, adds the ACP request surface the desktop app needs, and makes Goose advertise the MCP Apps extension to downstream MCP servers only when the connected client actually supports it.
In other words, this is the groundwork PR. It does not try to render anything in Goose2 yet, but it puts the ACP and MCP pieces in place so the later Goose2 PRs have something solid to build on.
If you're reviewing this slice and want to see how it's supposed to work, start with the sequence diagram and notes in #8592.
Related to #8592.