Claude-skill-registry atlassian-mcp

Use the Atlassian MCP Server to interact with JIRA from coding agents (Cursor, Claude Code). This skill documents how to use the official Atlassian MCP server for JIRA and Confluence operations. Enable this MCP server in your Cursor/Claude Code settings for JIRA access.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/atlassian-mcp" ~/.claude/skills/majiayu000-claude-skill-registry-atlassian-mcp-bcbbf0 && rm -rf "$T"
manifest: skills/data/atlassian-mcp/SKILL.md
source content

Atlassian MCP Server for JIRA

The Atlassian MCP Server provides direct access to JIRA and Confluence from coding agents. This is the supported way to access Atlassian data from Cursor or Claude Code.

Setup

In Cursor

The Atlassian MCP Server is already configured globally. To enable it:

  1. Open Cursor Settings
  2. Go to Tools & MCP
  3. Enable "Atlassian-MCP-Server"

Configuration location:

~/.cursor/mcp.json

{
  "mcpServers": {
    "Atlassian-MCP-Server": {
      "url": "https://mcp.atlassian.com/v1/sse"
    }
  }
}

In Claude Code

Add to your Claude Code MCP settings:

{
  "mcpServers": {
    "Atlassian-MCP-Server": {
      "url": "https://mcp.atlassian.com/v1/sse"
    }
  }
}

Available Tools

When enabled, the Atlassian MCP Server provides these tools:

Issue Operations

ToolDescription
mcp_Atlassian_getJiraIssue
Get details of a specific issue
mcp_Atlassian_createJiraIssue
Create a new issue
mcp_Atlassian_editJiraIssue
Update an existing issue
mcp_Atlassian_transitionJiraIssue
Change issue status
mcp_Atlassian_searchJiraIssuesUsingJql
Search issues with JQL

Comments

ToolDescription
mcp_Atlassian_addCommentToJiraIssue
Add a comment to an issue
mcp_Atlassian_getJiraIssueComments
Get comments from an issue

Confluence (if enabled)

ToolDescription
mcp_Atlassian_createConfluencePage
Create a Confluence page
mcp_Atlassian_getConfluencePage
Get a Confluence page
mcp_Atlassian_searchConfluence
Search Confluence

Common Patterns

Get Issue Details

Use mcp_Atlassian_getJiraIssue with issueKey: "PROJ-123"

Search for Issues

Use mcp_Atlassian_searchJiraIssuesUsingJql with:
  jql: "project = YOUR_PROJECT AND component = 'YOUR_COMPONENT' AND status = 'In Progress'"

Create an Issue

Use mcp_Atlassian_createJiraIssue with:
  project: "YOUR_PROJECT"
  issueType: "Story"
  summary: "Implement new feature"
  description: "Description of the feature"
  components: ["YOUR_COMPONENT"]

Transition Issue Status

Use mcp_Atlassian_transitionJiraIssue with:
  issueKey: "PROJ-123"
  transition: "In Progress"

Add Comment

Use mcp_Atlassian_addCommentToJiraIssue with:
  issueKey: "PROJ-123"
  comment: "Started working on this issue"

JQL Quick Reference

Common JQL queries for the Orient Task Force:

# All issues for YOUR_COMPONENT
project = YOUR_PROJECT AND component = "YOUR_COMPONENT"

# In Progress issues
project = YOUR_PROJECT AND component = "YOUR_COMPONENT" AND status = "In Progress"

# Blockers
project = YOUR_PROJECT AND component = "YOUR_COMPONENT" AND (priority = Blocker OR labels = blocked)

# Recent issues (last 7 days)
project = YOUR_PROJECT AND component = "YOUR_COMPONENT" AND created >= -7d

# My issues
project = YOUR_PROJECT AND component = "YOUR_COMPONENT" AND assignee = currentUser()

# Sprint issues
project = YOUR_PROJECT AND component = "YOUR_COMPONENT" AND sprint in openSprints()

Troubleshooting

"Tool not found" Error

Make sure the Atlassian MCP Server is enabled in your IDE settings. The tools won't appear until the server is connected.

Authentication Issues

The Atlassian MCP Server uses OAuth. If you're not authenticated:

  1. The tool will prompt you to authenticate
  2. Follow the OAuth flow in your browser
  3. Grant the necessary permissions

Rate Limits

The Atlassian MCP Server is subject to Atlassian's rate limits. If you hit limits:

  • Reduce query frequency
  • Use more specific JQL to reduce result sets
  • Cache results when appropriate