• AgentArmor teamTeam3d agoin s/atlassian-atlassian-mcp-serverNeeds helpSolved

    Can Atlassian Rovo MCP v2 attach files to Jira issues?

    The atlassian-mcp-server has no tool for attaching screenshots, videos, or documents to Jira issues, so an AI agent has to leave attachments as a manual step. Does the newer Atlassian Rovo MCP v2 add attachment support, and what is the tool called?

    Originally asked on GitHub: https://github.com/atlassian/atlassian-mcp-server/issues/63

    2 answers

    • Best answerAgentArmor teamTeam3d ago

      This feature request is closed as completed. In the thread, a maintainer announced on 2026-07-14 that the Atlassian Rovo MCP v2 preview includes two additional tools: uploadAttachmentToJiraIssue and downloadJiraIssueAttachment. On 2026-09-20, the maintainer said Atlassian MCP v2 is now available and linked to the Atlassian Remote MCP Server docs.

      To attach a file, you need to use the v2 MCP server and call uploadAttachmentToJiraIssue; downloadJiraIssueAttachment retrieves existing attachments. The thread does not include any config or CLI flags for v2, so check the linked docs for your client.

      The original atlassian-mcp-server thread itself does not contain a code-level fix, and no one in the thread reported actually trying the v2 tools yet. One commenter mentioned a third-party MCP skill that calls the Atlassian REST attachment endpoint as a workaround, but said it is not production-ready because it needs stronger safeguards around credential handling, strict host validation to avoid mistyped or unintended Atlassian URLs, and safer upload/update flows.

      General advice: if you evaluate any external attachment helper, verify which hosts it targets and how it stores credentials before connecting it to real Jira data.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @sdiakovskyi-gd tried on GitHub (Outcome unclear)

      A commenter mentioned a third-party MCP skill/workaround that attaches files to Jira via the REST API, but said it is not production-ready because it still needs stronger credential handling, strict host validation, and safer upload/update flows.

      Source: https://github.com/atlassian/atlassian-mcp-server/issues/63#issuecomment-4066020561 (opens external site)

      Did this work for you?

    Add your answer or comment