jira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_TYPE | No | 'cloud' or 'server' (optional, defaults to 'cloud') | cloud |
| JIRA_BASE_URL | Yes | Your Jira instance URL, e.g., https://your-domain.atlassian.net | |
| JIRA_API_TOKEN | Yes | API token for Cloud, PAT or password for Server/DC | |
| JIRA_AUTH_TYPE | No | 'basic' or 'bearer' (optional, defaults to 'basic') | basic |
| JIRA_USER_EMAIL | Yes | Your Jira account email (or username for Server/DC) | |
| JIRA_SKIP_SSL_VERIFY | No | 'true' to skip SSL verification (optional, defaults to 'false') | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_issuesB | Search JIRA issues using JQL |
| get_epic_childrenB | Get all child issues in an epic including their comments |
| get_issueA | Get detailed information about a specific JIRA issue including comments |
| create_issueB | Create a new JIRA issue |
| update_issueB | Update an existing JIRA issue |
| get_transitionsA | Get available status transitions for a JIRA issue |
| transition_issueC | Change the status of a JIRA issue by performing a transition |
| add_attachmentB | Add a file attachment to a JIRA issue |
| add_commentB | Add a comment to a JIRA issue |
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 9 tools
Each tool has a clearly distinct purpose: search vs. get specific issue vs. get epic children, get vs. perform transition, and add comment/attachment are well separated. Overlap is minimal and descriptions clarify boundaries.
All tool names follow a consistent snake_case verb_noun pattern (search_issues, get_issue, create_issue, etc.). The pattern is predictable throughout.
9 tools is a well-scoped set for JIRA issue management. Every tool earns its place, covering search, read, create, update, transitions, comments, and attachments without excess.
Core issue operations are present (search, get, create, update, transitions, comments, attachments), but lifecycle coverage is incomplete: no delete_issue, assign_issue, link_issue, or project/sprint operations. Agents may hit dead ends for deletion or assignment workflows.