Administrators would like the Atlassian Rovo MCP server to expose Jira project configuration that is already user‑visible in the Jira UI, specifically:

• Project Components
• Ability to list components for a given project (by key or ID).

For each component, return:

• id
• name
• description (if present)
• lead (accountId + displayName at least)
• defaultAssignee / assigneeType (if reasonably available)
• Component Leads
• Expose the component's lead information in a consistent shape that can be used by MCP clients to:
• Suggest who to tag for issues in a given component
• Route questions or approvals to the right owner
• Project Versions / Releases
• Ability to list all versions for a given project (by key or ID).

For each version, return:

• id
• name
• description
• released / archived
• releaseDate and startDate (if present)
• Some ordering or status metadata (e.g., released vs unreleased, or sequence as Jira returns it).

Why this matters:

Current Rovo MCP server Jira tools are issue‑centric (create/search/edit issues, transitions, etc.). However, components, component leads, and versions are core user‑visible project configuration in Jira.

Having MCP tools for these would allow MCP clients (e.g. VS Code, Rovo chat, custom MCP apps) to:

• Suggest appropriate components and component leads when users create or triage issues.
• List release trains / versions to correctly set Fix Version and coordinate work.
• Build richer automations and assistants that understand project ownership and release structure without requiring Jira admin APIs.

Requested scope:

• Read‑only operations only (no create/update/delete components or versions needed initially).
• Respect normal Jira permission model - only expose components/versions visible to the user whose credentials the MCP server is using.
• Ideally as part of the existing read_jira tool group in the Rovo MCP server.