chore(jira): restrict Atlassian MCP to Jira/Confluence capabilities

[cblecker]

Summary

• Adds capabilities query parameter to the Atlassian MCP server URL, scoping tool exposure to Jira, Confluence, and Atlassian search only
• Drops READ_COMPASS, WRITE_COMPASS, READ_JSM, and WRITE_JSM tool families that we don't use
• Bumps jira plugin to v0.7.0

Test plan

• Verify make lint passes
• Install the updated plugin and confirm Jira/Confluence MCP tools are available
• Confirm Compass and JSM tools are no longer exposed

Summary by CodeRabbit

Release Notes

• New Features
  • Jira plugin upgraded to version 0.7.0 with substantially expanded capabilities
  • Enhanced permissions now enabling comprehensive read, write, and search operations across Jira, Confluence, and Atlassian search platforms
  • Improved integration and operational flexibility for users managing Atlassian environments and content

[coderabbitai]

Walkthrough

Jira plugin version is bumped from 0.6.0 to 0.7.0 in the plugin manifest, marketplace registry, and documentation. MCP server endpoint configuration is expanded with capabilities query parameters granting read/write/search permissions for Jira, Confluence, and Atlassian operations.

Changes

Jira Plugin 0.7.0 Release

Layer / File(s)	Summary
Plugin version bump and MCP capabilities update plugins/jira/.claude-plugin/plugin.json, .claude-plugin/marketplace.json, docs/index.html, plugins/jira/.mcp.json	Jira plugin version incremented to 0.7.0 across manifest and published registries. MCP server endpoint configured with capabilities query parameters enabling read/write/search access for Jira, Confluence, and Atlassian search operations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

ok-to-test, lgtm

Suggested reviewers

• theobarberbany
• rvanderp3
• stbenjam

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: restricting the Atlassian MCP to specific capabilities for Jira and Confluence, which aligns with the primary objective of adding a capabilities query parameter to scope tool exposure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
No Real People Names In Style References	✅ Passed	No real people names found in style references, plugin commands, or documentation. PR only contains version bumps and MCP capability configuration changes.
No Assumed Git Remote Names	✅ Passed	PR modifies only jira plugin configuration files (.mcp.json, plugin.json) and marketplace registry. No git commands or assumed remote names (origin/upstream) appear in jira-specific changes.
Git Push Safety Rules	✅ Passed	PR contains only configuration file changes (version bumps and URL parameters) with no git push commands, force pushes, or any git operations.
No Untrusted Mcp Servers	✅ Passed	PR does not introduce any new MCP servers. It modifies the existing official Atlassian Rovo MCP server URL to restrict capabilities—a security-conscious change with no untrusted sources added.
Ai-Helpers Overlap Detection	✅ Passed	PR modifies only configuration and documentation files (not commands/skills/agents), triggering early termination rule: skip check when only modifying non-functional docs.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cblecker]

/hold
doing local testing

[cblecker]

Testing

Tested by adding the filtered URL as a second MCP server (atlassian-filtered) alongside the existing unfiltered one (plugin:jira:atlassian) and comparing the tool lists in the same session.

Unfiltered — 37 tools, including 6 Compass tools:

• createCompassComponent
• createCompassComponentRelationship
• createCompassCustomFieldDefinition
• getCompassComponent
• getCompassComponents
• getCompassCustomFieldDefinitions

Filtered (with ?capabilities=READ_JIRA,WRITE_JIRA,SEARCH_JIRA,READ_CONFLUENCE,WRITE_CONFLUENCE,SEARCH_CONFLUENCE,SEARCH_ATLASSIAN) — 31 tools, all 6 Compass tools removed.

No JSM tools appeared in either set — those require API token auth mode, and we use OAuth — so the filter's primary effect is dropping the 6 Compass tools that always fail with ProductNotFound / 403 against redhat.atlassian.net.

[cblecker]

/hold cancel

[cblecker]

/cc @stbenjam

[stbenjam]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cblecker, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• plugins/jira/OWNERS [cblecker,stbenjam]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment