| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ce CreateIssueApp to manage existing issue data
…server into mcp-ui-apps-3
When InsidersMode is enabled, append '(insiders)' to the User-Agent string sent with GitHub API requests, enabling server-side adoption tracking.
There was a problem hiding this comment.
Just tested this again, nice improvements! Some things I have noticed
What is the behaviour of these tools on hosts where MCP Apps is not supported? For example, in issue_write and create_pull_request, when Insiders is on and _ui_submitted is false, the tool early-returns a placeholder message like "Ready to create an issue". So it seems like on a host without MCP Apps support, users would get the placeholder text instead of the tool actually executing. I think we should have a way for people opting into insiders but using hosts that won't support Apps (which include 1P ones like Copilot CLI) to still be able to use the tool without the UI
On hover, the "Write" and "Preview" options in the markdown look inconsistent with the rich text options, in that they don't have rounded corners. A quick fix is to round the corners to make them consistent
In the markdown editor, the toolbar isn't responsive: I cannot scroll horizontally to reveal some of the options (like bullet point list, numbered list)
(nit) I have noticed that I cannot just pull up the create issue UI without populating it with title and body to create an issue. It only works by having the model write a test title and body, calling the issue_write tool and then showing the form pre-populated with that mock text for me to edit. Is that intentional? I wonder if we should let folks see an empty UI that they can fill out
(nit) maybe unrelated, but getting 422 error when trying to create a draft PR as it assumes my default branch is main but instead it's master. Don't think this was introduced with these changes but wanted to flag, maybe we can show a more helpful error message here
Sorry, something went wrong.
There was a problem hiding this comment.
Left a comment, but overall LGTM for Insiders!
Sorry, something went wrong.
| // This is a temporary workaround until the Go SDK adds an Extensions field | ||
| // to ClientCapabilities (see https://github.com/modelcontextprotocol/go-sdk/issues/777). | ||
| // Once that lands, detection should use capabilities.extensions instead. | ||
| var uiSupportedClients = map[string]bool{ |
There was a problem hiding this comment.
We could add Goose here too, as it also supports MCP Apps
Sorry, something went wrong.
There was a problem hiding this comment.
Overall LGTM for Insiders!
Sorry, something went wrong.
There was a problem hiding this comment.
Arshadigital.ir
Sorry, something went wrong.
| @@ -1,5 +1,5 @@ | |||
| .idea | |||
| cmd/github-mcp-server/github-mcp-server | |||
| cmd/github-mcp-server/github-mcp-server | ||
|
|
||
| # VSCode | ||
| .vscode/* |
| vendor | ||
| bin/ | ||
|
|
||
| # macOS |
| Back | FazBrowse Home | New Git URL |
Summary
Based on initial work by @tommaso-moro
This PR adds support for MCP Apps, enabling rich interactive UIs for MCP tools.
New MCP App UIs
Implementation
Insiders Mode
All MCP Apps functionality gated behind Insiders
These new UIs require a new React app that exists under the ui folder with components made available in iframes for clients that support the feature. This has been extensively tested under VSCode-Insiders.
This will require additional support in Remote MCP to ensure Insiders and resources support works correctly.
Why
As part of https://github.com/github/copilot-mcp-core/issues/1125
What changed
MCP impact
Prompts tested (tool changes only)
Security / limits
Tool renaming
Note: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
Docs