Schema | jira-mcp

jira-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`JIRA_URL`	Yes	The URL of your Jira instance (e.g., https://jira.telekom.de)
`JIRA_USERNAME`	Yes	Your Jira username (email)
`JIRA_API_TOKEN`	Yes	Your Jira personal access token or API token
`JIRA_AUTH_TYPE`	Yes	Authentication type (bearer for PAT, basic for basic auth)	bearer

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": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
get_ticketA	Fetch full details of a Jira ticket by its ID or key. Returns comprehensive ticket information including summary, description, status, issue type, priority, assignee, reporter, comments, and custom fields.
get_linked_ticketsA	Fetch all linked tickets and subtasks for a given Jira ticket. Returns issue links (blocks, is blocked by, relates to, etc.) and subtasks with their summaries and statuses.
update_ticket_statusA	Update the status of a Jira ticket by transitioning it to a new status. Validates that the transition is valid for the ticket's current workflow. Common statuses include: 'To Do', 'In Progress', 'In Review', 'Done'.

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/vaspap1790/jira-mcp'

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