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 tool 'example_tool' stands alone with a distinct purpose, so agents cannot misselect between multiple options.
The single tool name 'example_tool' follows a consistent snake_case pattern. Since there is only one tool, there is no inconsistency in naming conventions to evaluate.
A Jira MCP server with only one tool is too few for the apparent scope of Jira, which typically involves managing issues, projects, users, and workflows. This minimal tool count suggests an incomplete or trivial implementation.
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, updating, or querying issues, which are essential for the domain.