JIRA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_BASE_URL | Yes | Your JIRA instance URL (e.g., https://your-domain.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Your JIRA API token for authentication | |
| JIRA_USER_EMAIL | Yes | Email associated with your JIRA account |
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 |
|---|---|
| search_issuesB | Search JIRA issues using JQL |
| get_epic_childrenB | Get all child issues in an epic including their comments |
| get_issueA | Get detailed information about a specific JIRA issue including comments |
| create_issueB | Create a new JIRA issue |
| update_issueB | Update an existing JIRA issue |
| get_transitionsA | Get available status transitions for a JIRA issue |
| transition_issueC | Change the status of a JIRA issue by performing a transition |
| add_attachmentB | Add a file attachment to a JIRA issue |
| add_commentB | Add a comment to a JIRA 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 9 tools
Each tool has a clearly distinct purpose targeting specific JIRA operations: create, get, update, search, transition, add attachments/comments, and get epic children. There is no overlap or ambiguity between tools like 'get_issue' and 'search_issues' or 'update_issue' and 'transition_issue', making misselection unlikely.
All tools follow a consistent verb_noun naming pattern with snake_case throughout (e.g., create_issue, get_issue, update_issue). The verbs are appropriate and predictable, with no mixing of conventions or styles, ensuring readability and coherence.
With 9 tools, the server is well-scoped for JIRA operations, covering core workflows like issue management, searching, and status transitions. Each tool earns its place without being overly sparse or bloated, fitting typical server sizes of 3-15 tools.
The tool set provides strong coverage for JIRA issue lifecycle, including CRUD operations (create, get, update), searching, transitions, and attachments/comments. A minor gap exists with no delete_issue tool, but agents can work around this, and other operations like epic handling are partially covered.