mcp-server-atlassian-jira

aashari/mcp-server-atlassian-jira

3.5

If you are the rightful owner of mcp-server-atlassian-jira and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

A Node.js/TypeScript Model Context Protocol (MCP) server for Atlassian Jira Cloud, enabling AI systems to interact with Jira projects, issues, and comments securely.

Tools

Functions exposed to the LLM to take actions

jira_ls_projects

Lists Jira projects accessible to the user, optionally filtering by name/key (name) or sorting (orderBy). Use this to discover available projects and find project keys/IDs needed for other tools (like jira_get_project or jira_list_issues). Supports pagination via limit and startAt. Returns a formatted list of projects including key, name, type, style, lead, and URL. Pagination information including next page instructions is included in the returned text. Note: Default sort is by most recently updated issue time. Requires Jira credentials to be configured.

jira_get_project

Retrieves comprehensive details for a specific Jira project using its key or ID (projectKeyOrId). Includes description, lead, components, versions, and other metadata. Use this after finding a project key/ID via jira_list_projects to get its full details. Returns detailed project information formatted as Markdown. Requires Jira credentials to be configured.

jira_ls_issues

Searches for Jira issues using JQL and other filters. Supports filtering by project (projectKeyOrId), statuses (statuses), or advanced JQL queries (jql). Includes pagination via limit and startAt. Returns formatted issue summaries including key, type, status, summary, and assignee. The response includes the executed JQL query and pagination information with instructions for viewing the next page. Requires Jira credentials to be configured.

jira_get_issue

Retrieves comprehensive details about a specific Jira issue using its ID or key (issueIdOrKey). Returns formatted issue information including summary, description, status, reporter, assignee, comments summary, and related development information (commits, branches, pull requests) if available. Requires Jira credentials to be configured.

jira_ls_statuses

Lists available Jira statuses, either globally or for a specific project (projectKeyOrId). Use this to discover valid status names and IDs needed for filtering issues (e.g., in jira_ls_issues). Important: This tool returns all available statuses in a single response. The underlying Jira API does not support pagination for this endpoint, so parameters like limit or pagination tokens are not applicable. Returns a formatted Markdown list of statuses including name, ID, description, and category (To Do, In Progress, Done). Requires Jira credentials to be configured.

jira_ls_comments

Lists comments for a specific Jira issue identified by issueIdOrKey. Supports pagination via limit and startAt. Returns a formatted Markdown list of comments with author, date, and content. Pagination information including next page instructions is included in the returned text. Requires Jira credentials to be configured.

jira_add_comment

Adds a new comment to a specific Jira issue identified by issueIdOrKey. The content of the comment is provided in commentBody and supports Markdown formatting which will be converted to Jira's Atlassian Document Format (ADF). Returns a confirmation message and link to the newly created comment. Requires Jira credentials to be configured.

jira_ls_worklogs

List worklogs for a Jira issue. Shows all work logged on an issue including time spent, authors, and comments.

jira_add_worklog

Add a worklog entry to a Jira issue. Logs time spent working on an issue with optional comment and estimate adjustment.

jira_update_worklog

Update an existing worklog entry. Modify the time spent, comment, or start time of a previously logged work entry.

jira_delete_worklog

Delete a worklog entry from a Jira issue. Removes a previously logged work entry with optional estimate adjustment.

Prompts

Interactive templates invoked by user choice

No prompts

Resources

Contextual data attached and managed by the client

No resources