atlassian-mcp

Jira and Confluence automation via MCP protocol with JQL/CQL queries, ticket management, and sprint workflows. Load detailed guidance based on context: Note: Always load JIRA_API_TOKEN and CONFLUENCE_API_TOKEN from environment variables or a secrets manager — never hardcode credentials. When implementing Atlassian MCP features, provide: Documentation - Supports querying Jira issues with JQL filters, creating and updating tickets with custom fields, and managing sprints and backlogs - Enables searching, creating, and editing Confluence pages using CQL syntax with space and content management - Includes authentication patterns for OAuth 2.0, API tokens, and PAT credentials with permission scope validation - Provides reference guides for server setup, common workflows (issue triage, doc sync, sprint automation), and rate limit handling with pagination - 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 - Select server - Choose official cloud, open-source, or self-hosted MCP server - Authenticate - Configure OAuth 2.1, API tokens, or PAT credentials - Design...