Back to MCP Servers

Jira Slack integration for your AI agent

Integrate Jira MCP server into your Slack workspace for instant access to your AI agent.

Jira is the #1 agile project management tool used by teams to plan, track, release, and support great software with confidence

Categories

Productivity

Available Tools

Tools that your AI agent can use through this MCP server to interact with Jira

  • Update Issue

    Updates an issue. A transition may be applied and issue properties updated as part of the edit. See the documentation

  • Update Comment

    Updates a comment. See the documentation

  • Transition Issue

    Performs an issue transition and, if the transition has a screen, updates the fields from the transition screen. See the documentation

  • Search Issues with JQL

    Search for issues using JQL (Jira Query Language). See the documentation

  • Search Issues with JQL (POST)

    Searches for issues using JQL with enhanced search capabilities. See the documentation

  • Move Issues to Sprint

    Moves issues to a sprint, for a given sprint ID. See the documentation

  • List Sprints

    Returns all sprints from a board, for the given board ID. See the documentation

  • List Sprint Issues

    Returns all issues in a sprint. See the documentation

  • List Labels Options

    Retrieves available options for the Labels field.

  • List Issue Comments

    Lists all comments for an issue. See the documentation

  • List Epics

    Returns all epics from a board, for the given board ID. See the documentation

  • List Epic Issues

    Returns all issues that belong to an epic on the given board. See the documentation

  • List Boards

    Returns all boards. See the documentation

  • List Board Issues

    Returns all issues from a board, for the given board ID. See the documentation

  • Get Users

    Gets the details for a list of users. See the documentation

  • Get User

    Gets details of user. See the documentation

  • Get Transitions

    Gets either all transitions or a transition that can be performed by the user on an issue, based on the issue's status. See the documentation

  • Get Task

    Gets the status of a long-running asynchronous task. See the documentation

  • Get Sprint

    Returns the sprint for a given sprint ID. See the documentation

  • Get Issue

    Gets the details for an issue. See the documentation

  • Get Issue Types

    Gets the available issue types. If a project ID is provided, returns issue types for that project. Otherwise, returns all issue types accessible to the user. See the documentation

  • Get Issue Picker Suggestions

    Returns lists of issues matching a query string. See the documentation

  • Get Current User

    Returns the authenticated Jira user's account ID, display name, email, and active status. Call this first when the user says 'my issues', 'assigned to me', or needs their Jira identity. Use the returned accountId with Search Issues with JQL (e.g. assignee = '{accountId}') or Assign Issue. Requires a Cloud ID to identify the Jira site. See the documentation.

  • Get Cloud ID

    Lists all accessible Jira Cloud sites and their IDs. See the documentation

  • Get Board

    Returns the board for the given board ID. See the documentation

  • Get All Projects

    Gets metadata on all projects. See the documentation

  • Download Attachment

    Downloads a Jira issue attachment's binary content to the configured file-stash directory and returns its saved path plus the attachment's metadata (filename, mimeType, size, etc.). Use this after locating an attachment via Get Issue (its fields.attachment[] array lists each attachment's id, filename, size, and mimeType), or from an attachment reference surfaced by another Jira action or trigger — pass that id as attachmentId. The file is saved in the file-stash directory as <attachmentId>-<sanitized filename> (the ID prefix avoids collisions when multiple attachments share the same filename); the returned filedata tuple points at that saved path for use in downstream file-input props. Jira's content endpoint responds with a redirect to a signed, short-lived media URL — this is followed automatically, so no extra configuration is required. See the documentation

  • Delete Project

    Deletes a project. See the documentation

  • Create Jira Version in Project

    Creates a project version. See the documentation

  • Create Issue

    Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation

  • Create Future Sprint

    Creates a future sprint. See the documentation

  • Create Custom Field Options (Context)

    Create a context for custom field options. See the documentation.

  • Count Issues Using JQL

    Provide an estimated count of the issues that match the JQL. See the documentation

  • Check Issues Against JQL

    Checks whether one or more issues would be returned by one or more JQL queries. See the documentation

  • Assign Issue

    Assigns an issue to a user. See the documentation

  • Add Watcher To Issue

    Adds a user as a watcher of an issue by passing the account ID of the user, For example, 5b10ac8d82e05b22cc7d4ef5, If no user is specified the calling user is added. See the documentation

  • Add Multiple Attachments To Issue

    Adds multiple attachments to an issue. See the documentation

  • Add Comment To Issue

    Adds a new comment to an issue. See the documentation

  • Add Attachment To Issue

    Adds an attachment to an issue. See the documentation