Atlassian Attachments
Let your coding agent download Jira and Confluence Cloud attachment files by ID while you work tickets, specs, or runbooks.
Overview
Atlassian Attachments is a Build-phase MCP server that downloads Jira and Confluence Cloud attachments by attachment ID for agent workflows.
What is this MCP server?
- Download Jira Cloud attachments by attachment ID
- Download Confluence Cloud attachments by attachment ID
- stdio MCP server v0.1.2 installable via uvx from PyPI (mcp-atlassian-attachments)
- Atlassian Cloud Basic auth with HTTPS site URL, email, and API token
- Credentials configurable via env vars or ~/.config/mcp-atlassian-attachments/config.json
- Server version 0.1.2
- Transport: stdio
- Registry: PyPI identifier mcp-atlassian-attachments
What problem does it solve?
Agents and builders waste time opening Atlassian in the browser to grab files linked from issues or Confluence pages.
Who is it for?
Indie teams on Atlassian Cloud who want Claude or Cursor to pull ticket and wiki attachments during build or docs work.
Skip if: Self-hosted Jira/Data Center-only setups, full issue editing, or attachment upload and lifecycle management.
What do I get? / Deliverables
After you register the server with site URL, email, and API token, your agent can fetch attachment content by ID inside the coding session.
- Agent-callable download of Jira Cloud attachments by ID
- Agent-callable download of Confluence Cloud attachments by ID
Recommended MCP Servers
Journey fit
Solo builders wire Atlassian into the agent stack while implementing features, syncing PM artifacts, and pulling files linked from issues or pages. Attachments are fetched through MCP stdio tools instead of one-off curl scripts or browser downloads, which fits the integrations shelf for third-party SaaS bridges.
How it compares
MCP attachment downloader for Atlassian Cloud, not a full Jira/Confluence skill or marketplace plugin.
Common Questions / FAQ
Who is mcp-atlassian-attachments for?
Solo builders and small teams using Jira and Confluence Cloud who want their AI agent to download attachments by ID without manual browser steps.
When should I use mcp-atlassian-attachments?
Use it during build or docs workflows when specs, designs, or exports are stored as Jira or Confluence attachments and you need the agent to read or save those files.
How do I add mcp-atlassian-attachments to my agent?
Install via uvx (mcp-atlassian-attachments), set ATLASSIAN_SITE_URL, ATLASSIAN_EMAIL, and ATLASSIAN_API_TOKEN—or use config.json—and add the stdio server entry in your agent MCP configuration.