JIRA MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | Get details of a specific JIRA issue |
| jira_searchC | Search issues using JQL (JIRA Query Language) |
| jira_create_issueC | Create a new JIRA issue |
| jira_update_issueC | Update an existing JIRA issue |
| jira_transition_issueC | Transition an issue to a new status |
| jira_add_commentC | 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 6 tools
Each tool has a clearly distinct purpose targeting specific JIRA operations: creating, retrieving, updating, commenting on, searching for, and transitioning issues. There is no overlap or ambiguity between these functions.
All tools follow a consistent 'jira_verb_noun' pattern with snake_case throughout. The naming is predictable and uniform across all six tools.
Six tools is reasonable for a JIRA server, covering core issue management operations. It's slightly lean but includes essential CRUD and workflow actions, with minor gaps like missing project or user management.
The toolset covers key JIRA workflows: create, read, update, search, comment, and transition issues. Minor gaps exist, such as no delete operation or project-level tools, but agents can handle most common tasks effectively.