jira-minimal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_URL | Yes | Jira instance URL (e.g., https://xxx.atlassian.net) | |
| JIRA_USERNAME | Yes | Jira username/email | |
| JIRA_API_TOKEN | Yes | Jira API token |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jira_get_issueA | Get Jira issue by key (e.g., PROJ-123). Returns summary, status, type, assignee, and description. |
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 1 tool
With only one tool, there is no possibility of confusion or ambiguity between tools.
The single tool follows a consistent verb_noun pattern (jira_get_issue), so naming is perfectly consistent.
A single tool for a Jira server is too few; typical usage requires multiple operations like create, update, or search, making this feel incomplete despite the 'minimal' label.
Only a read operation is provided; missing essential operations like create, update, delete, and search, leaving the surface severely incomplete for any meaningful workflow.