mcp -jira

This MCP server exposes a set of JIRA-related tools that let you interact with Jira from the MCP interface. The available tools include listing tickets in the active sprint for a given project, fetching detailed information for a specific ticket, adding comments to tickets, linking two tickets with a relates-to relationship, updating a ticket description, listing child issues, and creating sub-tickets under a parent issue. To use them, configure the Jira MCP server in your Claude or MCP client settings, then invoke the desired tool with the required parameters. The tools are designed to work with standard Jira Cloud instances and rely on environment variables for authentication.

Usage flow:

• List sprint tickets: provide a projectKey to retrieve all tickets in the active sprint for that project.
• Get ticket details: provide an issueKey to fetch comprehensive information about a Jira issue.
• Add a comment: supply issueKey and comment to append a note to a ticket.
• Link tickets: specify sourceIssueKey and targetIssueKey to create a relates-to relationship between two issues.
• Update description: provide issueKey and the new description text.
• List child issues: provide a parentKey to fetch all child issues under a parent ticket.
• Create sub-ticket: provide parentKey and a summary; optional description and issueType can tailor the sub-task type.

Example shell snippet for invoking via the MCP UI:

<use_mcp_tool> <server_name>jira</server_name> <tool_name>list-sprint-tickets</tool_name> <arguments> { "projectKey": "YOUR_PROJECT_KEY" } </arguments> </use_mcp_tool>

Prerequisites:

• Node.js and npm installed on your system
• Access to the MCP environment (Claude or Cline) where you will run the Jira MCP server

Installation steps:

1. Clone or download the MCP server repository for Jira
2. Install dependencies

   npm install
   

3. Build the TypeScript code (required for environments where npx cannot directly execute TS files, e.g., certain Windows setups)

   npm run build
   

4. Configure the MCP settings in your MCP client (Claude or Cline) to point at this server. See the sections below for example configurations.
5. Start the server (development or production):
   • Development: npm run start:dev (watch mode)
   • Production: npm start (run compiled JS in dist)

Environment setup:

• Ensure you have the following environment variables configured in your MCP settings:
  • JIRA_HOST: Your Jira Cloud domain, e.g. https://your-domain.atlassian.net
  • JIRA_EMAIL: Your Jira account email
  • JIRA_API_TOKEN: A Jira API token generated from your Atlassian account

Example configuration (Claude):

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["path/to/this/repo/jira.ts"],
      "env": {
        "JIRA_HOST": "https://your-domain.atlassian.net",
        "JIRA_EMAIL": "your-email@example.com",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

Example configuration (Cline):

{
  "mcpServers": {
    "jira": {
      "command": "node",
      "args": ["path/to/this/repo/dist/jira.js"],
      "env": {
        "JIRA_HOST": "https://your-domain.atlassian.net",
        "JIRA_EMAIL": "your-email@example.com",
        "JIRA_API_TOKEN": "your-api-token"
      }
    }
  }
}

Environment variables are required for authentication with Jira. Ensure your JIRA_HOST uses the correct domain, and that the API token has permissions to read and modify issues as needed. If you encounter authentication errors, double-check the token scope and that there are no trailing spaces in environment values. When updating or creating issues, Jira may enforce fields like issue type or project key; supply appropriate values to avoid validation errors. If you update the code, remember to rebuild or restart the MCP server to pick up changes. If you run into issues starting the server on Windows, prefer the build step before attempting to run via npx, due to CLI script execution nuances described in the readme.