Skip to content

fix: gate MCP App UI resources on backing tool availability#2624

Open
advancedresearcharray wants to merge 1 commit into
github:mainfrom
advancedresearcharray:fix/ui-resources-read-only-2519
Open

fix: gate MCP App UI resources on backing tool availability#2624
advancedresearcharray wants to merge 1 commit into
github:mainfrom
advancedresearcharray:fix/ui-resources-read-only-2519

Conversation

@advancedresearcharray
Copy link
Copy Markdown

@advancedresearcharray advancedresearcharray commented Jun 6, 2026

Summary

  • Register MCP App UI resources only when their backing tool is present in the inventory (respects --read-only and other filters).
  • Add test coverage for read-only mode excluding write-tool UI resources while keeping get_me UI available.

Test plan

  • script/build-ui
  • go test ./pkg/github/... -run 'UIResource|RegistersUI' -count=1 -v
  • go test ./pkg/github/... -count=1

Closes #2519

@advancedresearcharray advancedresearcharray requested a review from a team as a code owner June 6, 2026 17:13
@advancedresearcharray advancedresearcharray force-pushed the fix/ui-resources-read-only-2519 branch 2 times, most recently from 5312f1a to 98f53a3 Compare June 6, 2026 17:16
Closes github#2519

UI resources for write tools were registered unconditionally even when
--read-only mode filtered out the backing tools. Register each UI resource
only when its companion tool passes inventory filters.
@advancedresearcharray advancedresearcharray force-pushed the fix/ui-resources-read-only-2519 branch from 98f53a3 to 00a795e Compare June 6, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP App UI resources for write tools are registered in --read-only mode

1 participant