jira-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira account email address | |
| JIRA_BASE_URL | Yes | Your Jira instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your Jira API token |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all accessible Jira projects |
| search_issuesB | Search for issues using a text query or JQL |
| get_issueB | Get full details of a specific Jira issue |
| create_issueC | Create a new Jira issue |
| get_transitionsA | Get available status transitions for an issue |
| transition_issueC | Change the status of a Jira issue |
| add_commentB | Add a comment to a Jira issue |
| get_boardsA | List all Scrum and Kanban boards |
| get_sprintsB | List sprints for a specific board |
| get_backlogB | Get issues in the backlog for a specific board |
| assign_issueB | Assign a Jira issue to a user |
| find_usersA | Search for Jira users by email or display name to get their accountId |
| get_myselfA | Get the profile details of the currently authenticated Jira user (the bot) |
| add_worklogB | Add a worklog to an issue (log hours worked) |
| add_attachmentB | Add a local file as an attachment to a Jira issue |
| create_sprintB | Create a new sprint on a board |
| update_sprint_stateA | Change the state of a sprint (e.g., start or complete) |
| get_project_versionsA | List all versions (releases) for a project |
| create_versionB | Create a new project version (release) |
| link_issuesB | Link two Jira issues (e.g., Blocks, Relates) |
| get_all_labelsB | Get all labels used in Jira |
| bulk_create_issuesB | Create multiple issues in a single request (max 50) |
| bulk_transition_issuesB | Transition multiple issues to a new status |
| create_subtaskC | Create a subtask for a parent issue |
| update_issueC | Update fields of an existing Jira issue |
| delete_issuesC | Delete one or more Jira issues |
| update_commentB | Update an existing comment on an issue |
| delete_commentC | Delete a comment from an issue |
| update_worklogB | Update an existing worklog entry |
| delete_worklogC | Delete a worklog entry |
| update_sprintC | Update sprint details (name, goal, dates) |
| delete_sprintsB | Delete one or more sprints |
| update_versionC | Update a project version/release |
| delete_versionsB | Delete one or more project versions |
| delete_issue_linkB | Remove a link between two issues |
| delete_attachmentA | Remove an attachment from an issue |
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 36 tools
Each tool targets a distinct resource and action, with clear separation between issues, comments, worklogs, sprints, versions, attachments, and user operations. Even similar-sounding tools like update_sprint and update_sprint_state are clearly differentiated by descriptions focusing on details vs state.
Most tools follow a verb_noun snake_case pattern, but there are minor singular/plural inconsistencies such as create_issue vs delete_issues and update_sprint vs delete_sprints. Bulk operations are consistently prefixed with bulk_, but delete operations also support bulk without a prefix.
With 36 tools, the server far exceeds the typical 3-15 tool range and crosses the 25-tool threshold for a well-scoped set. While Jira is complex, the breadth here feels heavy and could overwhelm agents.
The tool set provides strong CRUD coverage for issues, comments, worklogs, sprints, versions, and attachments, plus search, transitions, and linking. Minor gaps exist, such as no direct getters for comments or worklogs and no tool to list issue link types, but core workflows remain functional.