Jira MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Base URL, e.g. https://jira.company.com | |
| JIRA_PASSWORD | Yes | Jira password | |
| JIRA_USERNAME | Yes | Jira username | |
| JIRA_START_DATE_FIELD | No | Custom field ID for Start date | customfield_11300 |
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 |
|---|---|
| get_ticketA | Get full details of a Jira ticket by its key |
| transition_ticketC | Change the status of a Jira ticket by status name |
| update_ticketB | Update fields of a Jira ticket. Converting between a standard issue type and Sub-task is a Jira REST API limitation — use Jira's UI "Move" action instead. |
| add_commentB | Add a comment to a Jira ticket |
| search_ticketsC | Search Jira tickets using JQL query language |
| create_ticketB | Create a new Jira ticket |
| generate_release_notesB | Generate Markdown release notes for a fix version, grouped by issue type |
| link_issuesB | Create a link between two Jira tickets |
| log_workB | Log work (time) on a Jira ticket, optionally setting WorklogPRO Type of Work and Type of Activity |
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: get, transition, update, comment, search, create, release notes, link, and log work. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_ticket, add_comment, link_issues). No deviations.
9 tools cover core Jira ticket operations without being excessive. The count is well-scoped for the server's purpose.
Covers create, read, update, transition, search, comments, linking, release notes, and work logging. Missing delete ticket is a minor gap.