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 ambiguity or overlap between tools. The single tool 'example_tool' stands alone with a distinct purpose, so agents cannot misselect between multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'example_tool' follows a clear noun-based pattern, and with no other tools to compare, there are no inconsistencies in naming conventions.
A single tool is too few for a server named 'Jira MCP Server', which implies a domain related to Jira project management. This minimal set fails to cover the expected scope, such as CRUD operations for issues, projects, or workflows, making it inadequate for typical agent tasks.
The tool set is severely incomplete for the Jira domain. With only an 'example_tool' that processes messages, it lacks any operations for managing issues, projects, users, or other Jira entities, leaving obvious gaps that will cause agent failures in real-world scenarios.