@tarasrushchak/jira-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Jira instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_EMAIL | Yes | Email for Jira authentication | |
| JIRA_API_TOKEN | Yes | API token for Jira authentication | |
| CONFLUENCE_HOST | No | Confluence instance URL (optional, for Confluence tools) | |
| CONFLUENCE_EMAIL | No | Email for Confluence authentication (optional) | |
| CONFLUENCE_API_TOKEN | No | API token for Confluence authentication (optional) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ticketsB | List Jira tickets assigned to you |
| get_ticketC | Get details of a specific Jira ticket |
| create_ticketC | Create a new Jira ticket |
| search_ticketsB | Search for tickets in specific projects using text search |
| delete_issueB | Delete a Jira ticket |
| get_commentsB | Get comments for a specific Jira ticket |
| add_commentA | Add a comment to a Jira ticket. Supports mentions using [~accountId] or [~email@example.com] format. |
| delete_commentB | Delete a comment from a Jira ticket |
| delete_all_commentsB | Delete all comments from a Jira ticket |
| update_statusB | Update the status of a Jira ticket |
| get_transitionsC | Get available transitions for a Jira ticket |
| assign_ticketB | Assign a Jira ticket to a user |
| update_ticket_fieldsB | Update fields of a Jira ticket (e.g., original estimate, story points, labels, assignee, priority, due date, etc.) |
| get_ticket_fieldsA | Get all available fields and their metadata for a Jira ticket (useful for finding custom field IDs) |
| get_available_fieldsA | Get all available fields for a Jira ticket with their metadata and field IDs. Returns a mapping of field names to field IDs that can be used in update_ticket_fields. |
| add_worklogC | Add worklog (time spent) to a Jira ticket |
| get_worklogB | Get worklogs for a specific Jira ticket |
| update_worklogB | Update an existing worklog on a Jira ticket |
| delete_worklogB | Delete a worklog from a Jira ticket |
| create_issue_linkC | Create a link between two Jira issues |
| remove_issue_linkA | Remove a link between two Jira issues |
| get_all_projectsB | Get all Jira projects |
| get_project_issuesC | Get all issues for a specific project |
| get_project_versionsB | Get all versions for a project |
| create_versionC | Create a new version in a project |
| batch_create_issuesC | Create multiple Jira issues in a batch |
| get_agile_boardsC | Get all Agile boards for a project |
| get_board_issuesB | Get issues from an Agile board |
| get_sprints_from_boardB | Get all sprints from an Agile board |
| get_sprint_issuesC | Get issues from a sprint |
| search_usersA | Search for Jira users by email or display name to get their accountId for mentions |
| get_user_profileC | Get user profile information |
| get_kb_pageA | Get a Confluence/KB page by page ID or full URL. Returns page title, space, content (as plain text), version, and metadata. |
| search_kb_pagesA | Search for Confluence/KB pages by text, title, or CQL query. Returns matching pages with titles, spaces, and URLs. |
| get_kb_page_childrenA | Get child pages of a Confluence/KB page. Useful for navigating page hierarchies. |
| get_kb_page_commentsC | Get comments on a Confluence/KB page |
| get_kb_spacesA | List available Confluence/KB spaces. Useful for discovering space keys before searching. |
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 37 tools
Most tools have distinct purposes, but get_ticket_fields and get_available_fields appear to have overlapping descriptions, potentially causing confusion for an agent.
All tools follow a consistent verb_noun pattern with underscores, such as create_ticket, delete_comment, and search_users, making the naming predictable and easy to understand.
37 tools is on the higher side, but it is justified given the comprehensive coverage of both Jira and Confluence operations. The count is still reasonable for a full-featured server.
The tool set covers essential CRUD and lifecycle operations for Jira issues, comments, worklogs, and agile features, with some Confluence support. Missing create/update/delete for Confluence pages, but overall very solid.