fix(jira): filter Cloud-only tools on Server/Data Center - #1603
Merged
sooperset merged 1 commit intoAug 19, 2026
Conversation
Reported-by: AmirF194 Github-Issue: sooperset#1082
Contributor
|
@FullYolk, the production-registry coverage for both configured and header-based deployments is exactly what this fix needed. Thanks for closing the direct-call bypass as well as cleaning up Server/DC discovery. |
Contributor
Author
|
@sooperset Thanks for the review and merge! I’m glad the production-registry coverage and direct-call guard matched what the project needed. I appreciate the thoughtful feedback. |
|
Nice fix, and thanks for building on the diagnosis and adding the dispatch-time check too, that closes the discovery-bypass gap the original report didn't cover. |
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
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
Hide Jira tools backed exclusively by Cloud APIs from MCP discovery when the active Jira deployment is Server or Data Center. Apply the same capability check at dispatch time so a client cannot bypass discovery filtering by calling a hidden tool directly.
Fixes: #1082
Thanks to @AmirF194 for validating the behavior through the production server registration path and documenting the root cause in #1082.
Changes
jira_batch_get_changelogsandjira_move_issueas Cloud-only.JiraConfigor per-request Jira URL headers.Testing
main_mcpregistry lists both tools for Cloud and neither for Server/Data CenterChecklist