Jira

Jira MCP Server
  • typescript

6

GitHub Stars

typescript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "tbreeding-jira-mcp": {
      "command": "npx",
      "args": [
        "@timbreeding/jira-mcp-server@latest",
        "--jira-base-url=https://example.atlassian.net",
        "--jira-username=someJiraUserEmail@domain.com",
        "--jira-api-token=<your jira token>"
      ],
      "env": {
        "DEBUG": "true"
      }
    }
  }
}

You can interact with Jira through a dedicated MCP (Model Context Protocol) server that guides you through creating and updating issues with a unified, wizard-like experience. This MCP server exposes tools for querying Jira data, analyzing issues, and performing guided issue creation and updates in a consistent, robust flow.

How to use

You use an MCP client to connect to the Jira MCP Server and access its core Jira tools as well as the guided Issue Creation and Update Wizards. Start by establishing the MCP connection, then use the wizard to create new Jira issues or load existing ones, modify fields, and apply updates with a consistent workflow. You can monitor progress through the wizard’s state and status endpoints, and you can reset or reanalyze as needed.

How to install

Prerequisites you need before installing: Node.js and npm (Node package manager). You will run a local MCP client command to start the Jira MCP Server integration.

Installation steps

{
  "mcpServers": {
    "JiraMCP_Published": {
      "command": "npx",
      "args": [
        "@timbreeding/jira-mcp-server@latest",
        "--jira-base-url=https://example.atlassian.net",
        "--jira-username=someJiraUserEmail@domain.com",
        "--jira-api-token=<your jira token>"
      ],
      "env": {
        "DEBUG": "true",
        "LOG_FILE_PATH": "" // Some full path. If blank, it will not write logs to a file.
      }
    }
  }
}

Run and test with MCP Inspector

For local development and testing with the MCP Inspector, you can start the server with the required environment variables and run the app, ensuring you have built the project if needed.

Environment and security considerations

  • Environment variables shown here control logging and log file handling. Use a secure Jira base URL, user email, and API token. Treat the Jira API token as sensitive data and avoid exposing it in logs or shared code. If you need to run without file logging, leave LOG_FILE_PATH blank.

Notes on usage with the Issue Creation and Update Wizards

The Jira MCP Server provides two guided experiences: the Issue Creation Wizard and the Unified Issue Update Workflow. The creation wizard walks you through selecting a project, choosing an issue type, retrieving and populating fields, optionally analyzing details, and finally creating the issue. The update workflow loads an existing issue into a common state, applies field updates, and then persists changes through a unified update path. You can inspect the internal wizard state and status, reset the wizard when needed, and run analysis to inform your updates.

Troubleshooting tips

If you encounter authentication or API access issues, verify your Jira base URL, user email, and API token. Ensure the token has the required permissions for the actions you perform. When logs are enabled, check the log file path provided by LOG_FILE_PATH or the console output if you left it blank.

Available tools

getJiraIssue

Fetches a Jira issue by its key.

analyzeJiraIssue

Performs comprehensive analysis of a Jira issue.

jiraGet

Fetches data from any Jira API GET endpoint.

getIssuesByJql

Searches for Jira issues using a JQL query.

issueCreation_getState

Gets the current internal state of the wizard.

issueCreation_getStatus

Gets the high-level status of the wizard.

issueCreation_initiateState

Initializes a new wizard state.

issueCreation_resetState

Resets the wizard state.

issueCreation_updateState

Updates the wizard state (project, issue type, fields, step).

issueCreation_createIssue

Creates a Jira issue using the wizard's state.

issueCreation_getProjects

Retrieves available Jira projects.

issueCreation_getIssueTypes

Gets available issue types for the selected project.

issueCreation_getFields

Retrieves fields required for the selected project/issue type.

issueCreation_updateFields

Updates specific field values in the wizard state.

issueCreation_setAnalysisComplete

Sets the analysis complete flag.

issueCreation_setUserConfirmation

Sets the user confirmation flag before creation.

issueCreation_analyzeIssue

Analyzes the issue details within the wizard context.

issueUpdateWizard_loadIssueIntoState

Fetch a Jira issue by key and load it into the state for unified updates.

issueUpdateWizard_updateIssueFromState

Update the loaded issue using the current state.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational