Skip to main content
Glama
sina-haseli

mcp-server-jira

by sina-haseli

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_BASE_URLYesBase URL of the Jira instance, e.g. https://jira.yourcompany.com
JIRA_API_TOKENYesAPI token / password used for Basic Auth
JIRA_USER_EMAILYesAccount email/username used for Basic Auth
JIRA_PROJECT_KEYYesProject key, e.g. PRD
JIRA_STORY_ISSUE_TYPENoIssue type name for storiesStory
JIRA_OUTLINE_LINK_FIELDNoCustom field id for the Outline link (e.g. customfield_10100)
JIRA_STORY_POINTS_FIELDNoCustom field id for story pointscustomfield_10016

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_storyA

Creates a new Jira Story from a PRD. Formats the description with acceptance criteria and an optional Outline PRD link, sets labels and priority, and (if an Outline URL is supplied) attaches it as a remote link. Returns the created issue key, id, and browse URL.

get_storyA

Retrieves a Story by its issue key (e.g. PRD-42). Returns the key fields an AI agent needs: summary, description, status, labels, priority, and browse URL.

update_storyA

Updates fields of an existing Story (e.g. after human approval edits). Only the fields you supply are changed. Returns { success, key }.

search_storiesA

Searches for Stories in the configured project using a plain-text query (wrapped in JQL). Useful for checking duplicates before creating a new Story. Returns an array of { key, summary, status, labels, url }.

get_project_infoA

Returns metadata for a Jira project: project key/name, available priorities, and the issue type id for Stories. Defaults to the configured project; pass project_key to target another. Use this to validate input before creating issues.

add_commentA

Adds a plain-text comment to a Story. Used, for example, to log when the PRD doc is updated in Outline. Returns { success, comment_id }.

transition_storyA

Moves a Story through its workflow (e.g. To Do -> In Progress -> Done). Call without transition to list available transitions. Transitions into a terminal status (Done/Closed/Resolved) are guarded and require confirm:true.

delete_storyA

PERMANENTLY deletes a Story by issue key. This is irreversible. Guarded: without confirm:true it returns a warning instead of deleting. Intended for human-approved cleanup only.

list_projectsA

Lists all Jira projects visible to the account. Returns key, name, id and project type for each. Use this to discover which project_key to pass to other tools when working across multiple projects.

create_projectA

Creates a new Jira project (admin only). Guarded: requires confirm:true. Some Jira versions require a template_key; if creation fails for that reason, retry with template_key.

create_issue_typeA

Creates a new issue type in Jira (admin only). Guarded: requires confirm:true. Issue types are global across the instance.

list_boardsA

Lists Jira Software Agile boards (scrum/kanban). Returns board id, name and type. The board id is needed to list sprints and fetch burndown data. Requires Jira Software (Agile) on the instance.

list_sprintsA

Lists sprints for a given Agile board. Returns sprint id, name, state, and start/end dates. Use the sprint id with get_sprint_burndown. Requires a scrum board.

get_sprint_burndownA

Returns burndown data for a sprint so the AI can analyze/summarize progress (this is data, not a rendered chart image). Includes a reliable computed summary (committed vs completed vs remaining story points, issue counts by status) plus best-effort raw GreenHopper burndown time-series. Requires Jira Software.

create_boardA

Creates a Jira Software Agile board (scrum/kanban) from an existing saved filter. Guarded: requires confirm:true. Requires Jira Software and permission to manage boards.

create_sprintA

Creates a sprint on a scrum board. Guarded: requires confirm:true. Requires Jira Software.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sina-haseli/mcp-server-jira'

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