jira-attachment-mcp
Fetches Jira issue attachments, returning inline images or cached file paths.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jira-attachment-mcpfetch attachment 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jira-attachment-mcp
A tiny local MCP server that fetches Jira attachments and returns them to an MCP client such as Claude Code.
Images (PNG, JPEG, GIF, WebP) under ~3 MB are returned inline, so the model can see them directly.
Larger images and all other file types are saved to
~/.cache/jira-attachment-mcp/and the local path is returned.
It runs over stdio and exposes a single tool, jira_get_attachment, which takes
a numeric Jira attachment ID.
Prerequisites
Node.js >= 18
An Atlassian API token: https://id.atlassian.com/manage-profile/security/api-tokens
Related MCP server: Jira MCP Integration
Setup
npm install
node setup.jssetup.js prompts for your Atlassian email, API token, and Jira base URL
(e.g. https://your-company.atlassian.net), then writes them to
~/.config/jira-attachment-mcp/config.json with 0600 permissions.
Then register the server with Claude Code (use the absolute path to index.js):
claude mcp add --transport stdio jira-attach -- node /absolute/path/to/index.jsRestart Claude Code (or reload MCP servers) so the new server is picked up.
Security
Your credentials never leave your machine and are never committed: they live
only in ~/.config/jira-attachment-mcp/config.json (mode 0600). The token is
used solely to build the HTTP Basic auth header for requests to your own Jira
instance.
Licence
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Artifact store for AI agents — read, write, and search files by path; share by rendered URL.
- uploads.shOAuthsh.uploads
Host files from coding agents; stage on a branch and attach to GitHub PRs.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud and Server/Data Center deployments for issue management, project tracking, and workflow automation. Supports multiple authentication methods including API tokens, OAuth 2.0, and personal access tokens.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Jira Cloud through the REST API, supporting project management, issue operations (create, read, update, delete), JQL search, task assignments, and status transitions.-
- AlicenseNot gradedqualityAmaintenanceProvides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.MIT
- AlicenseNot gradedqualityAmaintenanceEnables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.217 npm2MIT