- Home
- Skills
- Jeffallan
- Claude Skills
- Atlassian Mcp
atlassian-mcp_skill
- HTML
110
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill jeffallan/claude-skills --skill atlassian-mcp- SKILL.md4.0 KB
Overview
This skill is an expert integration guide and toolkit for connecting Jira, Confluence, and other Atlassian tools to AI systems via the Model Context Protocol (MCP). It focuses on secure authentication, robust query design (JQL/CQL), and production-ready workflows that automate issue triage, documentation sync, and sprint planning. Use it to design, test, and deploy MCP-based Atlassian integrations while preserving permissions and observability.
How this skill works
The skill inspects and prepares MCP server configuration, authentication flows (OAuth 2.1, API tokens, PATs), and example JQL/CQL queries, then generates tool-call implementations with pagination, rate-limit handling, and error recovery. It validates queries before execution, recommends permission scopes, and provides templates for logging, retry strategies, and safe deployment. The output includes JSON config snippets, query examples with explanations, and concrete call patterns for Jira and Confluence REST endpoints.
When to use it
- Querying Jira issues with complex JQL filters or building saved searches
- Searching, creating, or updating Confluence pages using CQL
- Automating sprint workflows, backlog grooming, and issue triage
- Setting up MCP server authentication and selecting official vs open-source servers
- Syncing meeting notes to Jira tickets or generating docs from issue data
Best practices
- Always validate and sanitize user-provided JQL/CQL before running queries
- Use OAuth or scoped API tokens; never hardcode secrets in code or logs
- Handle pagination (50–100 items/page) and respect rate-limit headers with exponential backoff
- Test with read-only operations and verify permission boundaries before write actions
- Log API calls and errors without exposing sensitive issue content
Example use cases
- Build an MCP-backed bot that triages incoming bug reports into Jira using JQL filters and automated labels
- Sync Confluence meeting notes into project Jira tickets with links and structured metadata
- Create a CI job that runs scheduled CQL searches to generate status dashboards in Confluence
- Migrate or connect self-hosted Atlassian instances to an open-source MCP server for AI access
- Implement a permission-aware workflow that prompts for confirmation before updating production issues
FAQ
Prefer OAuth 2.1 for user-scoped actions and scoped API tokens or PATs for service integrations; never mix methods in a single session.
How should I handle large result sets?
Use pagination (50–100 items per page) and implement exponential backoff when encountering rate-limit responses; log progress for auditing.