Skip to main content

​
At a glance

  • Availability: Enabled by default.
  • Auth: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: read:jira-work, write:jira-work, read:jira-user, offline_access.

​
Credentials

Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.
VariableRequiredDescription
ATLASSIAN_CLIENT_IDYesAtlassian OAuth 2.0 Client ID (from your app) Docs.
ATLASSIAN_CLIENT_SECRETYesAtlassian OAuth 2.0 Client Secret Docs.

​
Tools

ToolAccessDescription
List Atlassian SitesReadList Atlassian cloud sites/resources the OAuth token can access; use the returned id as cloudId for Jira and Confluence tools
List ProjectsReadList all accessible Jira projects
Get ProjectReadGet detailed information about a Jira project
Search IssuesReadSearch Jira issues using JQL (Jira Query Language)
Get IssueReadGet detailed information about a specific Jira issue
Create IssueWriteCreate a new Jira issue in a project
Update IssueWriteUpdate an existing Jira issue (status, fields, etc.)
List CommentsReadList comments on a Jira issue
Add CommentWriteAdd a comment to a Jira issue
Get TransitionsReadList available workflow transitions for a Jira issue
Transition IssueWriteMove a Jira issue to a new workflow status. First call get_transitions to get valid transition IDs, then pass the ID here.
Search UsersReadSearch Jira users by name or email to find the accountId needed for assigning issues

​
Example prompts

  • Search for all open bugs assigned to me or in my current sprint.
  • Create a new task in Jira with a title, description, and priority.
  • Get a summary of all issues in the current sprint, organized by status.
  • Move an issue to a different status (To Do, In Progress, Done, etc.).