We are using the Atlassian Remote MCP Server (Model Context Protocol) integration to connect Claude to our Jira instance for internal automation workflows.

Currently, the OAuth scopes exposed by the Atlassian MCP app do not include manage:jira-project. This is blocking our ability to programmatically create Jira projects through the MCP integration, which is a core part of our internal tooling.

Request:
Please add the manage:jira-project OAuth 2.0 scope to the set of scopes available/requestable by the Atlassian Remote MCP Server app, so that project-creation operations (createProject / equivalent Jira REST endpoints under /rest/api/3/project) can be authorized through the MCP connector.

Business justification:

• Without this scope, we must fall back to manual project creation in the Jira UI, which bypasses our automated governance checks and increases the risk of inconsistent project setup.
• This is a standard Jira admin-level permission already used elsewhere in our workflows; we are only requesting it be exposed through the MCP OAuth consent flow.

Environment:

• Product: Jira Cloud
• Integration: Atlassian Remote MCP Server (https://mcp.atlassian.com/v1/mcp)
   
  Current scopes: