Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_HOSTYesThe URL of your Jira instance (e.g., https://your-domain.atlassian.net)
JIRA_EMAILYesYour email address for Jira authentication
JIRA_API_TOKENYesYour Jira API token

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_projectsA

Retrieve all Jira projects accessible to the authenticated user. Returns project keys, names, IDs, and basic metadata. Use this to discover available projects before creating issues or performing other operations.

get_issue_typesA

Get all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values.

create_issueA

Create a new Jira issue (Bug, Story, Task, Epic, etc.) or subtask. Returns the created issue key, ID, and URL. Use get_issue_types to find valid issueType values for the project. To create a subtask, specify the parent issue key.

get_issueA

Retrieve detailed information about a specific Jira issue including status, assignee, description, comments, and workflow data. Use this to get current state before making updates.

update_issueA

Update fields of an existing Jira issue or convert to subtask. Only provided fields will be updated. Use get_issue first to see current values. Returns success confirmation.

delete_issueA

Permanently delete a Jira issue. This action cannot be undone. Use with caution. Returns success confirmation.

create_commentA

Add a comment to a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool). Returns comment ID and creation details.

get_commentsB

Get comments for a Jira issue with pagination support. Returns comments with pagination metadata to help navigate through large comment lists.

update_commentB

Update an existing comment on a Jira issue. Supports plain text or Markdown for rich formatting (headings, lists, code blocks, links, etc.). Markdown is automatically converted to ADF. For mentions, use format: @[accountId:displayName] (get accountId from get_users tool).

delete_commentC

Delete a comment from a Jira issue

get_transitionsC

Get available transitions for a Jira issue

transition_issueC

Move a Jira issue to a different status/state

assign_issueC

Assign a Jira issue to a user

get_usersC

Search for users in Jira

get_current_userB

Get information about the current authenticated user

get_sprintsB

Get all sprints for a specific board. Returns sprint information including ID, name, state, and dates.

move_issue_to_sprintB

Move an issue to a specific sprint. This is the main function to add tickets to the current sprint.

get_sprint_issuesB

Get all issues in a specific sprint. Useful for viewing what tickets are currently in a sprint.

get_agile_boardsA

Get all agile boards available in the Jira instance. Required to find board IDs for sprint operations.

delete_sprintA

Delete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.

create_sprintC

Create a new sprint. Sprint name and origin board ID are required. Start date, end date, and goal are optional.

update_sprintA

Update sprint information (name, dates, goal, state). Only provided fields will be updated. For closed sprints, only name and goal can be updated.

close_sprintA

Close and complete a sprint. This action requires the sprint to be in the "active" state. Once closed, the sprint cannot be reopened.

query_wikiC

Get Confluence page content by specific code (like F4CjNw).

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

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