mcp-atlassian-attachments
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_EMAIL | Yes | Your email address associated with the Atlassian account | |
| ATLASSIAN_SITE_URL | Yes | Your Atlassian site URL, e.g., https://yourorg.atlassian.net | |
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian API token with at least read:jira-work scope |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| download_jira_attachmentA | [Atlassian] Download Jira attachment by ID to a local directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools.
The single tool uses a clear verb_noun pattern (download_jira_attachment), consistent with good naming conventions.
The server is named 'attachments' but provides only a download tool; this is far too few for the implied scope.
Missing fundamental operations like upload, delete, or list attachments, leaving agents with a dead-end workflow.