Skip to content

fix(jira): filter Cloud-only tools on Server/Data Center - #1603

Merged
sooperset merged 1 commit into
sooperset:mainfrom
FullYolk:fix/filter-cloud-only-jira-tools
Aug 19, 2026
Merged

fix(jira): filter Cloud-only tools on Server/Data Center#1603
sooperset merged 1 commit into
sooperset:mainfrom
FullYolk:fix/filter-cloud-only-jira-tools

Conversation

@FullYolk

@FullYolk FullYolk commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

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

  • Tag jira_batch_get_changelogs and jira_move_issue as Cloud-only.
  • Derive Jira deployment capability from the startup JiraConfig or per-request Jira URL headers.
  • Filter deployment-incompatible tools during discovery and reject direct calls before execution.
  • Add regression coverage for Cloud and Server/Data Center discovery, header-based deployments, and direct-call defense.

Testing

  • Unit tests added/updated
  • Integration tests passed (no live Jira instance required for this change)
  • Manual checks performed: verified the production main_mcp registry lists both tools for Cloud and neither for Server/Data Center

Checklist

  • Code follows project style guidelines (linting passes).
  • Tests added/updated for changes.
  • All tests pass locally (3,830 passed; 4 unrelated Windows-specific tests fail on path, timestamp, MIME, and POSIX permission behavior).
  • Documentation updated (no generated content changed; the documentation consistency check passes).

@sooperset
sooperset merged commit a213816 into sooperset:main Aug 19, 2026
8 checks passed
@mcp-atlassian-maintainer

Copy link
Copy Markdown
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.

@FullYolk

Copy link
Copy Markdown
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.

@AmirF194

Copy link
Copy Markdown

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.

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.

[Bug]: Cloud-Only Tools Exposed to Agents When Connected to Server/Data Center

3 participants