Atlassian Jira MCP Server

A powerful Model Context Protocol (MCP) server that provides comprehensive integration with Atlassian Jira. This server enables AI assistants and applications to interact seamlessly with Jira's project management capabilities, including managing issues, projects, sprints, comments, worklogs, and more. Whether you're automating workflows, building intelligent project management tools, or simply need programmatic access to your Jira instance, this server provides all the essential capabilities through a clean, well-structured interface.

Overview

The Atlassian Jira MCP Server bridges the gap between AI applications and Jira's robust project management platform. It exposes Jira's REST API functionality through MCP tools, allowing for sophisticated automation and integration scenarios. From basic operations like creating and updating issues to advanced features like sprint management and JQL-based searching, this server provides comprehensive coverage of Jira's core functionality.

This integration is ideal for teams looking to enhance their project management workflows with AI capabilities, automate repetitive tasks, generate reports, or build custom applications that need deep Jira integration. The server handles authentication and API communication, providing a simplified interface for complex Jira operations.

Features

Complete Issue Management

Full lifecycle management of Jira issues including creation, updates, deletion, and detailed retrieval. Support for all standard issue fields including summaries, descriptions, assignees, priorities, labels, components, and due dates. Handle complex scenarios like parent-child relationships for subtasks.

Advanced Search Capabilities

Powerful JQL (Jira Query Language) search functionality allowing you to find issues based on complex criteria. Support for field selection, result expansion, and pagination to efficiently handle large result sets.

Project Organization

Access and manage Jira projects with the ability to list all projects, retrieve detailed project information, and expand additional data like descriptions and project leads.

Agile Board and Sprint Support

Complete integration with Jira's Agile features including board management, sprint retrieval, and sprint issue tracking. Filter boards by type (Scrum/Kanban) and sprints by state (active, closed, future).

Workflow Management

Handle issue transitions and status changes through Jira's workflow system. Retrieve available transitions for any issue and execute transitions with optional comments and resolutions.

Collaboration Features

Comprehensive comment management including adding, updating, deleting, and retrieving comments. Support for worklog tracking to record time spent on issues with detailed descriptions and timestamps.

User Management

Search for users across your Jira instance and retrieve information about the authenticated user. Essential for assignment operations and user-related queries.

Filter and Version Management

Access saved filters including favorite filters, retrieve filter details, and manage project versions/releases with creation and retrieval capabilities.

Attachment Handling

Retrieve metadata for issue attachments, providing visibility into files associated with your issues.

Tools

Project Tools

list_projects

Get a list of all projects accessible to the authenticated user.

Parameters:

• expand (optional): Additional data to include such as "description,lead"
• maxResults (optional): Maximum number of results to return (default: 50)

get_project

Retrieve detailed information about a specific project.

Parameters:

• projectIdOrKey (required): The project ID or project key
• expand (optional): Additional data to include in the response

Issue Search and Retrieval

search_issues

Search for issues using JQL (Jira Query Language) with advanced filtering and field selection.

Parameters:

• jql (required): JQL query string (e.g., "project = PROJ AND status = Open")
• fields (optional): Array of specific fields to return (default: all fields)
• expand (optional): Additional data to expand in the response
• startAt (optional): Starting index for pagination (default: 0)
• maxResults (optional): Maximum number of results (default: 50)

get_issue

Get comprehensive details of a specific issue by its ID or key.

Parameters:

• issueIdOrKey (required): Issue ID or issue key (e.g., "PROJ-123")
• fields (optional): Array of specific fields to return
• expand (optional): Additional data to expand (e.g., "changelog,renderedFields")

Issue Management

create_issue

Create a new issue in a specified project with full field support.

Parameters:

• projectKey (required): Project key (e.g., "PROJ")
• summary (required): Issue summary/title
• issueType (required): Issue type (e.g., "Bug", "Task", "Story")
• description (optional): Detailed issue description
• assignee (optional): Assignee account ID
• priority (optional): Priority name (e.g., "High", "Medium", "Low")
• labels (optional): Array of labels to add
• components (optional): Array of component names
• duedate (optional): Due date in YYYY-MM-DD format
• parentKey (optional): Parent issue key for creating subtasks

update_issue

Update an existing issue's fields.

Parameters:

• issueIdOrKey (required): Issue ID or key to update
• summary (optional): New summary text
• description (optional): New description text
• assignee (optional): Assignee account ID
• priority (optional): Priority name
• labels (optional): Array of labels (replaces existing labels)
• duedate (optional): Due date in YYYY-MM-DD format

delete_issue

Permanently delete an issue from Jira.

Parameters:

• issueIdOrKey (required): Issue ID or key to delete
• deleteSubtasks (optional): Whether to delete associated subtasks (default: false)

assign_issue

Assign an issue to a specific user.

Parameters:

• issueIdOrKey (required): Issue ID or key
• accountId (required): Account ID of the user to assign (use "-1" for automatic assignment, "null" for unassigned)

Workflow and Transitions

get_transitions

Retrieve all available transitions for an issue based on its current status and workflow.

Parameters:

• issueIdOrKey (required): Issue ID or key

transition_issue

Move an issue through its workflow to a different status.

Parameters:

• issueIdOrKey (required): Issue ID or key
• transitionId (required): Transition ID obtained from get_transitions
• comment (optional): Comment to add with the transition
• resolution (optional): Resolution name (e.g., "Done", "Won't Do")

Comments

get_comments

Retrieve all comments on a specific issue.

Parameters:

• issueIdOrKey (required): Issue ID or key
• maxResults (optional): Maximum number of results (default: 50)

add_comment

Add a new comment to an issue.

Parameters:

• issueIdOrKey (required): Issue ID or key
• comment (required): Comment text content

update_comment

Update the text of an existing comment.

Parameters:

• issueIdOrKey (required): Issue ID or key
• commentId (required): Comment ID to update
• comment (required): New comment text

delete_comment

Delete a comment from an issue.

Parameters:

• issueIdOrKey (required): Issue ID or key
• commentId (required): Comment ID to delete

Worklogs

get_worklogs

Retrieve all time tracking worklogs for an issue.

Parameters:

• issueIdOrKey (required): Issue ID or key

add_worklog

Log time spent working on an issue.

Parameters:

• issueIdOrKey (required): Issue ID or key
• timeSpent (required): Time spent in Jira format (e.g., "3h 30m", "1d 2h")
• comment (optional): Description of the work performed
• started (optional): Start date/time in ISO 8601 format

Agile Boards and Sprints

list_boards

Get all boards accessible to the authenticated user.

Parameters:

• projectKeyOrId (optional): Filter boards by project key or ID
• type (optional): Board type filter ("scrum" or "kanban")
• maxResults (optional): Maximum number of results (default: 50)

get_board_sprints

Retrieve all sprints associated with a specific board.

Parameters:

• boardId (required): Board ID
• state (optional): Sprint state filter ("active", "closed", or "future")

get_sprint_issues

Get all issues that belong to a specific sprint.

Parameters:

• sprintId (required): Sprint ID
• maxResults (optional): Maximum number of results (default: 50)

User Management

search_users

Search for users in your Jira instance by name or email.

Parameters:

• query (required): Search query string (name or email)
• maxResults (optional): Maximum number of results (default: 50)

get_current_user

Retrieve information about the currently authenticated user.

Parameters: None

Filters

get_favorite_filters

Get all filters marked as favorites by the current user.

Parameters: None

get_filter

Retrieve detailed information about a specific saved filter.

Parameters:

• filterId (required): Filter ID

Attachments

get_attachments

Get metadata for all attachments on an issue.

Parameters:

• issueIdOrKey (required): Issue ID or key

Versions

get_project_versions

Retrieve all versions/releases defined for a project.

Parameters:

• projectIdOrKey (required): Project ID or key

create_version

Create a new version/release in a project.

Parameters:

• projectId (required): Project ID
• name (required): Version name
• description (optional): Version description
• releaseDate (optional): Release date in YYYY-MM-DD format
• released (optional): Boolean indicating whether the version is released

Use Cases

The Atlassian Jira MCP Server enables a wide range of automation and integration scenarios:

• Automated Issue Creation: Automatically create issues from external events, customer feedback, or monitoring alerts
• Smart Reporting: Generate custom reports by querying issues with JQL and aggregating data
• Workflow Automation: Build intelligent workflows that transition issues based on complex conditions
• Time Tracking: Automate worklog entries and time tracking based on activities in other systems
• Sprint Planning: Programmatically manage sprint contents and retrieve sprint metrics
• Notification Systems: Monitor issue changes and comments to trigger notifications or actions
• Data Synchronization: Keep Jira synchronized with other project management or development tools
• AI-Assisted Project Management: Enable AI assistants to help manage projects, update issues, and answer questions about project status

Best Practices

When using this MCP server, consider the following best practices:

Use JQL Effectively: Master JQL syntax to create precise queries that return exactly the data you need, reducing unnecessary API calls and improving performance.

Pagination: For large result sets, use the pagination parameters (startAt and maxResults) to retrieve data in manageable chunks.

Field Selection: When retrieving issues, specify only the fields you need using the fields parameter to reduce response size and improve performance.

Transition Workflow: Always use get_transitions before attempting to transition an issue to ensure the transition is valid for the current state.

Account IDs: When assigning issues or searching users, remember that Jira uses account IDs rather than usernames for user identification.

Error Handling: Implement proper error handling as operations may fail due to permissions, workflow restrictions, or validation errors.

This MCP server provides a robust foundation for integrating Jira into your AI-powered workflows and applications, enabling sophisticated project management automation and intelligent assistance.