Jira & Linear Integration

Issue Tracker Integration (Jira & Linear)

Claude Code streamlines your development workflow by bridging the gap between project management tools and your terminal. By connecting to Jira or Linear via the Model Context Protocol (MCP), Claude gains the ability to contextually understand tasks, implement requirements against specific acceptance criteria, and manage ticket lifecycles without leaving the codebase.

Key Capabilities

• Requirement Analysis: Claude reads ticket descriptions and acceptance criteria to ensure implementations align with business requirements.
• Workflow Automation: Automatically transition tickets (e.g., from "In Progress" to "In Review") when a PR is created.
• Bi-directional Sync: Claude can create new bug tickets directly from the terminal if it discovers issues during development or testing.
• Contextual Linking: Automatically includes ticket IDs in commit messages and links PRs back to the original issue.

Configuration

Integration is handled through the .mcp.json file in your project root. This file tells Claude which MCP servers to use to communicate with your ticketing provider.

1. Configure the MCP Server

Add your preferred provider to your .mcp.json configuration. You will need to provide the necessary API tokens or environment variables as required by the specific MCP implementation.

{
  "mcpServers": {
    "jira": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-jira"],
      "env": {
        "JIRA_URL": "https://your-domain.atlassian.net",
        "JIRA_API_TOKEN": "your-api-token",
        "JIRA_EMAIL": "your-email@company.com"
      }
    },
    "linear": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-linear"],
      "env": {
        "LINEAR_API_KEY": "your-linear-api-key"
      }
    }
  }
}

2. The /ticket Command

The project includes a specialized command located at .claude/commands/ticket.md. This command acts as the entry point for issue-based development.

Usage:

/ticket [ISSUE-ID]

When you run this command, Claude performs the following sequence:

1. Fetch: Retrieves the issue details (title, description, and AC) from Jira or Linear.
2. Plan: Analyzes the codebase and proposes a technical plan to satisfy the requirements.
3. Execute: Performs the necessary file edits and runs tests.
4. Verify: Checks the work against the acceptance criteria retrieved in step 1.
5. Status Update: Updates the ticket status to reflect that the work is ready for review.

Working with Acceptance Criteria

One of the most powerful features of this integration is Claude’s ability to "check off" acceptance criteria. Because Claude has direct access to the ticket data, you can prompt it to:

"Review the current implementation of the authentication logic and confirm it meets all ACs in JIRA-123."

Claude will then map the code logic to the ticket's bullet points, highlighting any discrepancies or missing edge cases before you even open a PR.

Automated PR Linking

If you have the GitHub Action configured alongside the Jira/Linear integration, Claude will automatically append the ticket link to your PR description, ensuring your project management board stays in sync with your version control system.