mcp-server-atlassian-jira
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_API_TOKEN | Yes | Your Atlassian API token | |
| ATLASSIAN_SITE_NAME | Yes | Your Atlassian site name (e.g., yourdomain.atlassian.net) | |
| ATLASSIAN_USER_EMAIL | Yes | Your Atlassian account email | |
| FORCE_HTTPS_FALLBACK | No | Set to 'true' to force the node:https transport fallback |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_getA | Read any Jira data. Returns TOON format by default (30-60% fewer tokens than JSON). IMPORTANT - Cost Optimization:
Schema Discovery Pattern:
Output format: TOON (default, token-efficient) or JSON ( Common paths:
JQ examples: Example JQL queries: API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_postA | Create Jira resources. Returns TOON format by default (token-efficient). IMPORTANT - Cost Optimization:
Output format: TOON (default) or JSON ( Common operations:
API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_putA | Replace Jira resources (full update). Returns TOON format by default. IMPORTANT - Cost Optimization: Use Output format: TOON (default) or JSON ( Common operations:
Note: PUT replaces the entire resource. For partial updates, prefer PATCH. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_patchA | Partially update Jira resources. Returns TOON format by default. IMPORTANT - Cost Optimization: Use Output format: TOON (default) or JSON ( Common operations:
Note: PATCH only updates the fields you specify, leaving others unchanged. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_deleteB | Delete Jira resources. Returns TOON format by default. Output format: TOON (default) or JSON ( Common operations:
Note: Most DELETE endpoints return 204 No Content on success. API reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/ |
| jira_attachA | Upload a file attachment to a Jira issue. Two ways to attach files:
Supported file types: Images (png, jpg, gif), documents (pdf, doc, xls), text (txt, csv, json, md, log), archives (zip, tar), code files, and more. Returns: Attachment metadata including ID, filename, size, and URL. To list existing attachments: Use jira_get with:
|
| jira_get_attachmentA | Download a Jira attachment to a local file. Usage: Parameters:
To find attachment IDs: Use jira_get with:
Returns: Download result with file path, filename, MIME type, and size. |
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 7 tools
Each tool maps to a distinct HTTP verb or operation (e.g., attach, delete, get, patch, post, put) with clear boundaries. Even jira_get_attachment (download) is separate from jira_get (read data) and jira_attach (upload).
All tools follow the 'jira_' prefix with an HTTP-method-like verb (attach, delete, get, get_attachment, patch, post, put). The naming is consistent, predictable, and clearly indicates the action.
With 7 tools covering core CRUD, file attachment, and flexible generic operations, the count is well-scoped for a Jira server. It provides sufficient functionality without unnecessary bloat.
The tool set covers all major CRUD operations and file attachments. While jira_get handles searches and listings, a dedicated search tool could improve completeness, but the current surface is largely complete for common Jira workflows.