jira-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Email address used for Jira API authentication. | |
| JIRA_DOMAIN | Yes | Jira site domain, for example your-company.atlassian.net. | |
| JIRA_API_TOKEN | Yes | Jira API token for the account above. |
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 |
|---|---|
| fetch_jiraD | – |
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 with other tools. The tool's purpose is unambiguous within the set, even without a description.
The single tool name 'fetch_jira' follows a clear verb_noun pattern, consistent with common naming conventions. There are no other tools to cause inconsistency.
A single tool for a Jira server is far too few to cover typical operations like creating, updating, or deleting issues. It falls in the 'too few' category, making the server feel incomplete for its apparent purpose.
The server only provides a 'fetch' operation, lacking any create, update, delete, or search capabilities. This severely limits its usefulness for Jira workflows, leaving huge gaps in functionality.