Schema | Jira MCP

Jira MCP

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

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/namcpgem/gem-jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server