mcpField
A
atlassian-mcp

atlassian-mcp

github.com/jeffallanProductivity12.1k4.4k installsUpdated today
Repository

About atlassian-mcp

Atlassian MCP Expert is a skill for working with Jira and Confluence through MCP integrations. It guides server selection, authentication, query design, permission checks, and operational workflows, including guidance for both Atlassian Cloud and Server/Data Center.

Key features

  1. 01Jira JQL query guidance
  2. 02Confluence CQL search guidance
  3. 03MCP server selection and setup
  4. 04OAuth and token authentication guidance
  5. 05Permission and rate-limit handling

Use cases

  1. 01Find and triage Jira issues
  2. 02Search or create Confluence pages
  3. 03Sync meeting notes to Jira tickets
  4. 04Configure Atlassian MCP access

MCP support

The skill guides configuration of Atlassian Cloud's hosted Rovo MCP Server or the community mcp-atlassian server for Server/Data Center. It covers authentication, queries, permissions, and MCP tool workflows.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jeffallan/claude-skills --skill atlassian-mcp

After installing, type/atlassian-mcpin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
authentication-patterns.md
common-workflows.md
confluence-operations.md
jira-queries.md
mcp-server-setup.md

Details

From the project README

Atlassian MCP Expert

When to Use This Skill

  • Querying Jira issues with JQL filters
  • Searching or creating Confluence pages
  • Automating sprint workflows and backlog management
  • Setting up MCP server authentication (OAuth/API tokens)
  • Syncing meeting notes to Jira tickets
  • Generating documentation from issue data
  • Debugging Atlassian API integration issues
  • Choosing between official vs open-source MCP servers

Core Workflow

  1. Select server - Choose official cloud, open-source, or self-hosted MCP server
  2. Authenticate - Configure OAuth 2.1, API tokens, or PAT credentials
  3. Design queries - Write JQL for Jira, CQL for Confluence; validate with maxResults=1 before full execution
  4. Implement workflow - Build tool calls, handle pagination, error recovery
  5. Verify permissions - Confirm required scopes with a read-only probe before any write or bulk operation
  6. Deploy - Configure IDE integration, test permissions, monitor rate limits

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Server Setupreferences/mcp-server-setup.mdInstallation, choosing servers, configuration
Jira Operationsreferences/jira-queries.mdJQL syntax, issue CRUD, sprints, boards, issue linking
Confluence Opsreferences/confluence-operations.mdCQL search, page creation, spaces, comments
Authenticationreferences/authentication-patterns.mdOAuth 2.0, API tokens, permission scopes
Common Workflowsreferences/common-workflows.mdIssue triage, doc sync, sprint automation

Quick-Start Examples

JQL Query Samples
# Open issues assigned to current user in a sprint
project = PROJ AND status = "In Progress" AND assignee = currentUser() ORDER BY priority DESC

# Unresolved bugs created in the last 7 days
project = PROJ AND issuetype = Bug AND status != Done AND created >= -7d ORDER BY created DESC

# Validate before bulk: test with maxResults=1 first
project = PROJ AND sprint in openSprints() AND status = Open ORDER BY created DESC
CQL Query Samples
# Find pages updated in a specific space recently
space = "ENG" AND type = page AND lastModified >= "2024-01-01" ORDER BY lastModified DESC

# Search page text for a keyword
space = "ENG" AND type = page AND text ~ "deployment runbook"
Minimal MCP Server Configuration

Atlassian Cloud: connect to the hosted Atlassian Rovo MCP Server, then run /mcp to sign in with OAuth.

claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp

Server/Data Center: run the community mcp-atlassian server (sooperset) with personal access tokens.

{
  "mcpServers": {
    "atlassian": {
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://jira.internal.example.com",
        "JIRA_PERSONAL_TOKEN": "${JIRA_PERSONAL_TOKEN}",
        "CONFLUENCE_URL": "https://confluence.internal.example.com",
        "CONFLUENCE_PERSONAL_TOKEN": "${CONFLUENCE_PERSONAL_TOKEN}"
      }
    }
  }
}

Note: Always load tokens from environment variables or a secrets manager; never hardcode credentials. Tool names differ between servers, see references/mcp-server-setup.md.

Constraints

MUST DO
  • Respect user permissions and workspace access controls
  • Validate JQL/CQL queries before execution (use maxResults=1 probe first)
  • Handle rate limits with exponential backoff
  • Use pagination for large result sets (50-100 items per page)
  • Implement error recovery for network failures
  • Log API calls for debugging and audit trails
  • Test with read-only operations first
  • Document required permission scopes
  • Confirm before any write or bulk operation against production data
MUST NOT DO
  • Hardcode API tokens or OAuth secrets in code
  • Ignore rate limit headers from Atlassian APIs
  • Create issues without validating required fields
  • Skip input sanitization on user-provided query strings
  • Deploy without testing permission boundaries
  • Update production data without confirmation prompts
  • Mix different authentication methods in same session
  • Expose sensitive issue data in logs or error messages

Output Templates

When implementing Atlassian MCP features, provide:

  1. MCP server configuration (JSON/environment vars)
  2. Query examples (JQL/CQL with explanations)
  3. Tool call implementation with error handling
  4. Authentication setup instructions
  5. Brief explanation of permission requirements

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

Comments

Markdown supported