Agent skill · software engineering · sundial-org
mcp-atlassian
Run the Model Context Protocol (MCP) Atlassian server in Docker, enabling integration with Jira, Confluence, and other Atlassian products. Use when you need to query Jira issues, search Confluence, or interact with Atlassian services programmatically. Requires Docker and valid Jira API credentials.
Why this skill is useful
Adds an executable script for running the MCP Atlassian server with Docker, enabling programmatic access to Jira and Confluence that the AI cannot generate on its own.
What it needs
Requires docker installed locally. Requires jira account access. About 1k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
MCP Atlassian Overview The MCP Atlassian server provides programmatic access to Jira and other Atlassian services through the Model Context Protocol. Run it in Docker with your Jira credentials to query issues, manage projects, and interact with Atlassian tools. Quick Start Pull and run the container with your Jira credentials: With script (faster): Run the bundled script with your API token: Environment Variables JIRAURL: Your Atlassian instance URL (e.g., https://company.atlassian.net) JIRAUSERNAME: Your Jira email address JIRAAPITOKEN: Your Jira API token (create in Account Settings → Security) Using MCP Atlassian with Clawdbot Once running, the MCP server exposes Jira tools for use. Reference the container as an MCP source in your Clawdbot config to query issues, create tasks, or manage Jira directly from your agent. Resources scripts/ runmcpatlassian.sh - Simplified runner script with credential handling
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/mcp-atlassian