jira-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_TOKEN | No | Bearer token for authentication. If set, takes priority over username/password. | |
| JIRA_BASE_URL | No | The base URL of your Jira instance, e.g. https://your-jira-instance.com | |
| JIRA_PASSWORD | No | Password for basic authentication. | |
| JIRA_USERNAME | No | Username for basic authentication. |
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 |
|---|---|
| jira_searchB | Search Jira issues using JQL |
| jira_get_issueC | Retrieve Jira issue details |
| jira_create_issueC | Create a Jira task |
| jira_add_commentC | Add comment to issue |
| jira_assign_issueC | Assign issue to user |
| jira_transition_issueC | Move issue to another workflow state |
| jira_projectsC | Get Jira projects |
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 7 tools
Each tool targets a distinct Jira operation: search, retrieve, create, comment, assign, transition, and list projects. There is no overlap or ambiguity between them.
All tools share the 'jira_' prefix and use snake_case, with most following a verb_noun pattern (e.g., jira_get_issue). The exception is jira_projects, which is a simple noun rather than 'list_projects', but this is a minor deviation.
With 7 tools, the server is well-scoped for common Jira operations. Each tool covers a core feature without unnecessary bloat or missing essentials.
The set covers create, read, search, comment, assign, and transition, but lacks an update operation (e.g., jira_update_issue), which is a core part of issue lifecycle management. This is a notable gap that agents may need to work around.