agentleFS
santiago-migonisantiago-migoni/claude-skills/skills/atlassian-mcp/SKILL.md

atlassian-mcp

Skill0 starsChanged 11 months agoMITView on GitHub

Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, or debugging Atlassian API integrations.

11 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 6 are common, 0 are distinctive, and 1 is very specific to this project.

  • 6

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Design queries: - Write JQL for Jira, CQL for Confluence.

    line 34
  2. Common:

    Use pagination for large result sets (50-100 items per page)

    line 105
  3. Common:

    Test with read-only operations first

    line 108
  4. Common:

    Document required permission scopes

    line 109
  5. Common:

    Create issues without validating required fields

    line 115
  6. Common:

    Update production data without confirmation prompts

    line 118
  7. Common:

    When implementing Atlassian MCP features, provide:

    line 124

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.