Problem / Gap

Atlassian's official Remote MCP Server for Jira (mcp.atlassian.com) currently has no tool that exposes the Bulk Get Workflows API.
The Bulk Get Workflows API is the current, supported endpoint, which returns full transition rule definitions:

•  Restrict transition (conditions)
•  Request input (screens / input required on transition)
•  Validate details (validators)
•  Perform actions (post functions)

Because no MCP tool surfaces this endpoint, any organization connecting Jira to an AI assistant through Atlassian's own MCP server cannot read workflow rules programmatically, regardless of the user's actual Jira permissions. This blocks legitimate, permission-respecting automation and analysis use cases (e.g., auditing workflow rules, explaining why a transition is blocked, documenting workflow configuration).

Requested Feature

Add a tool to the Atlassian Remote MCP Server (either a pre-declared tool or a discovery operation) that:

 1.  Wraps the Bulk get workflows REST API.
 2.  Returns transition rule configuration for a given project or workflow, specifically:

•  Restrict transition (conditions)
•  Request input (screens/inputs)
•  Validate details (validators)
•  Perform actions (post functions)
 3.  Respects the caller's existing Jira permissions, i.e., it should be available to anyone who has view workflow access in Jira, and return only what the caller is already entitled to see.