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
- 01Jira JQL query guidance
- 02Confluence CQL search guidance
- 03MCP server selection and setup
- 04OAuth and token authentication guidance
- 05Permission and rate-limit handling
Use cases
- 01Find and triage Jira issues
- 02Search or create Confluence pages
- 03Sync meeting notes to Jira tickets
- 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-mcpAfter installing, type/atlassian-mcpin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/authentication-patterns.mdcommon-workflows.mdconfluence-operations.mdjira-queries.mdmcp-server-setup.mdDetails
From the project READMEAtlassian 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
- Select server - Choose official cloud, open-source, or self-hosted MCP server
- Authenticate - Configure OAuth 2.1, API tokens, or PAT credentials
- Design queries - Write JQL for Jira, CQL for Confluence; validate with
maxResults=1before full execution - Implement workflow - Build tool calls, handle pagination, error recovery
- Verify permissions - Confirm required scopes with a read-only probe before any write or bulk operation
- Deploy - Configure IDE integration, test permissions, monitor rate limits
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| Server Setup | references/mcp-server-setup.md | Installation, choosing servers, configuration |
| Jira Operations | references/jira-queries.md | JQL syntax, issue CRUD, sprints, boards, issue linking |
| Confluence Ops | references/confluence-operations.md | CQL search, page creation, spaces, comments |
| Authentication | references/authentication-patterns.md | OAuth 2.0, API tokens, permission scopes |
| Common Workflows | references/common-workflows.md | Issue 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=1probe 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:
- MCP server configuration (JSON/environment vars)
- Query examples (JQL/CQL with explanations)
- Tool call implementation with error handling
- Authentication setup instructions
- Brief explanation of permission requirements
Maintained by @jeffallan, Principal Consultant at Synergetic Solutions