MCP JIRA 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 |
|---|---|
| echoC | Echo back the input text with optional case transformation |
| create_jira_issueC | Creates a new JIRA issue from Markdown description. |
| update_jira_issueC | Updates an existing JIRA issue. Only provided fields will be updated. |
| search_jira_issuesC | Search for Jira issues using JQL (Jira Query Language) syntax |
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 4 tools
Three JIRA-related tools have clear distinct purposes: create, search, and update issues. However, the 'echo' tool is completely unrelated to the JIRA domain, which creates a minor but noticeable ambiguity in the toolset's overall purpose. The JIRA tools themselves are well-differentiated.
The three JIRA tools follow a consistent verb_noun pattern with underscores (create_jira_issue, search_jira_issues, update_jira_issue). However, the 'echo' tool breaks this pattern by using a single word without the JIRA prefix, creating mixed conventions within the set. The naming is readable but not fully consistent.
With only 4 tools, the count feels thin for a JIRA server, especially given that one tool ('echo') is unrelated to JIRA. For a domain as rich as JIRA issue management, having just three core tools (create, search, update) is borderline minimal, lacking expected operations like delete, get details, or comment management.
The toolset has significant gaps for JIRA issue management. While it covers create, search, and update, it lacks essential operations like deleting issues, retrieving specific issue details, adding comments, or managing attachments. The inclusion of an unrelated 'echo' tool further dilutes the domain coverage, making the surface incomplete for typical JIRA workflows.