Jira and Linear MCP Integration

Your PM just assigned you a ticket with a two-paragraph description and six acceptance criteria. You open your editor, try to remember what the ticket said, start coding, and realize halfway through that you missed a requirement. Then you switch back to Jira, re-read the ticket, copy the acceptance criteria, paste them into a comment in your code, and start over. This context-switching loop repeats dozens of times per sprint.

Project management MCP servers break this loop. The AI reads the ticket directly, understands the requirements, and can even update the ticket status when the work is done.

What You’ll Walk Away With

• Setup for Atlassian Rovo MCP (Jira + Confluence) and Linear MCP
• Prompts for ticket-driven development workflows
• Automation patterns for status updates and ticket creation
• Guidelines for combining project management MCP with version control

Atlassian Rovo MCP (Jira + Confluence)

The official Atlassian MCP server is a remote server that connects via OAuth 2.1. It provides access to Jira issues, Confluence pages, and Compass components.

Cursor

{
  "mcpServers": {
    "atlassian": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"]
    }
  }
}

Claude Code

{
  "mcpServers": {
    "atlassian": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/mcp"]
    }
  }
}

Codex

[mcp.atlassian]
transport = "http"
url = "https://mcp.atlassian.com/v1/mcp"

Tip

Copy-paste prompt for ticket-driven development:

“Search Jira for the highest-priority open bug assigned to me. Read its description, acceptance criteria, and any linked Confluence documentation. Then create a feature branch named after the ticket ID, implement the fix based on the requirements, and write a commit message that references the ticket.”

Linear MCP

For teams using Linear, the Linear MCP integration provides issue management, cycle tracking, and project updates.

Tip

Copy-paste prompt for sprint planning:

“List all issues in the current cycle that are in ‘Todo’ status. For each one, read the description and estimate the complexity. Suggest an implementation order based on dependencies and complexity, and flag any issues that are underspecified or missing acceptance criteria.”

Tip

Copy-paste prompt for automated ticket creation:

“I just found a bug: the password reset email contains a broken link when the user’s email has a plus sign in it. Create a Jira bug ticket in the AUTH project with priority High, include steps to reproduce, expected behavior, and actual behavior. Assign it to me.”

Combining PM MCP with Version Control

The most powerful workflow combines project management and version control MCP servers. The AI reads the ticket, creates a branch, writes the code, opens a PR referencing the ticket, and updates the ticket status — all in one conversation.

1. Read the ticket. The AI fetches requirements and acceptance criteria from Jira or Linear.
2. Create the branch. Using Git MCP, the AI creates a feature branch named after the ticket ID.
3. Implement the change. The AI writes code grounded in the ticket’s requirements.
4. Open a PR. Using GitHub MCP, the AI creates a pull request that references the ticket.
5. Update the ticket. The AI moves the ticket to “In Review” and adds a comment with the PR link.

When This Breaks

OAuth flow never completes. The Atlassian Rovo MCP requires a browser redirect to localhost. If you are behind a VPN or corporate proxy that blocks localhost callbacks, the OAuth flow will hang. Try disconnecting from the VPN temporarily or using a direct connection.

“Your site admin must authorize this app” error. The first user on your Atlassian site must have access to both Jira and Confluence for the initial OAuth consent. Ask your Atlassian admin to complete the first authorization.

AI cannot find the ticket. Ensure you are using the correct project key. The AI searches using JQL, so “find open bugs in PLATFORM” requires the project key to be “PLATFORM”, not the project name.

Permission denied on ticket updates. The MCP server respects your Atlassian permissions. If you cannot edit a ticket in the Jira web UI, the AI cannot edit it through MCP either.

What’s Next

Atlassian Rovo MCP Deep Dive Advanced workflows for Jira, Confluence, and Compass.

Design Tools MCP Figma and design system integration.