JIRA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_TYPE | No | Type of Jira instance: 'cloud' or 'server' (default: 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 | Authentication type: 'basic' or 'bearer' (default: basic) | basic |
| JIRA_USER_EMAIL | Yes | Your Jira account email |
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 targets a distinct action: attachments, comments, creation, retrieval of issues/epics, transitions, search, and updates. There is no overlap in purpose, ensuring clear differentiation.
All tool names follow a consistent verb_noun pattern (e.g., add_attachment, get_issue, search_issues) using lowercase with underscores. No naming irregularities exist.
With 9 tools, the server covers essential JIRA operations—CRUD, comments, attachments, transitions, and search—without being bloated or sparse. The count is well-scoped for an issue management server.
The tool set covers core issue lifecycle (create, read, update, transition, search, comment, attach) but lacks a delete tool. However, JIRA often relies on transitions rather than deletion, so the gap is minor.