JIRA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_HOST | Yes | Your JIRA instance URL (e.g., https://your-instance.atlassian.net) | |
| JIRA_USERNAME | Yes | Your JIRA email address/username | |
| JIRA_API_TOKEN | Yes | Your JIRA API token (paste exactly as provided by Atlassian, may contain special characters) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_issueC | Retrieves detailed information about a specific JIRA issue |
| jira_get_issue_commentsC | Retrieves comments for a specific JIRA issue with configurable quantity and filtering options |
| jira_get_assigned_issuesB | Retrieves all JIRA issues assigned to the current user |
| jira_create_issueC | Creates a new JIRA issue with specified parameters |
| jira_update_issueC | Updates an existing JIRA issue with field changes, status transitions, and worklog entries |
| search_jira_issuesB | Search JIRA issues using JQL queries or helper parameters. Supports both expert JQL and beginner-friendly filters. |
| jira_get_projectsC | Get all accessible JIRA projects with filtering and search capabilities |
| jira_get_boardsC | Get all accessible JIRA boards with filtering by type, project, and name |
| jira_get_sprintsC | Get all sprints for a specific JIRA board with filtering by state |
| jira_add_worklogC | Add a worklog entry to track time spent on an issue |
| jira_get_worklogsC | Get all worklog entries for a specific issue |
| jira_update_worklogC | Update an existing worklog entry |
| jira_delete_worklogC | Delete a worklog entry from an issue |
| jira_get_current_userB | Get current user profile information and permissions |
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 14 tools
Every tool has a clearly distinct purpose targeting specific JIRA resources and actions. For example, jira_get_issue retrieves a single issue, jira_get_assigned_issues gets user-assigned issues, and search_jira_issues handles complex queries, with no overlap that would cause confusion. The worklog tools (add, delete, get, update) are similarly well-differentiated.
All tools follow a consistent jira_verb_noun naming pattern throughout, such as jira_create_issue, jira_get_projects, and jira_update_worklog. This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or structure.
With 14 tools, the server is well-scoped for JIRA operations, covering core areas like issues, projects, boards, sprints, worklogs, and user management. Each tool earns its place by addressing a specific need without bloat, typical for a domain-specific server.
The tool set provides strong coverage for JIRA's core workflows, including CRUD for issues and worklogs, project/board/sprint management, and search capabilities. Minor gaps exist, such as no tools for managing comments (only retrieving them) or handling attachments, but agents can work around these with the available tools.