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 |
|---|---|
| example_toolC | An example tool that processes messages |
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 overlap between tools. The single tool 'example_tool' has a distinct purpose by default, as there are no other tools to compare it to.
The naming is trivially consistent because there is only one tool. The tool name 'example_tool' follows a snake_case pattern, and with no other tools, there is no inconsistency to evaluate.
A single tool is too few for a Jira MCP server, which typically involves managing issues, projects, workflows, and other entities. This minimal set suggests an incomplete or placeholder implementation, failing to cover the expected domain scope.
The tool set is severely incomplete for a Jira server. With only an 'example_tool' that processes messages, there are no tools for core Jira operations like creating, retrieving, updating, or deleting issues, projects, or other resources, leaving significant gaps that will cause agent failures.