Skip to main content
Glama
alexeydubinin

HH JIRA MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
search_team_active_portfoliosD
create_taskD
set_defence_checkedD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.6/5.0

Scored across 3 tools

Disambiguation5/5

The three tools have clearly distinct purposes: create_task handles task creation, search_team_active_portfolios handles portfolio searching, and set_defence_checked handles defence status updates. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency3/5

The naming is mixed in conventions: create_task and set_defence_checked follow a verb_noun pattern, while search_team_active_portfolios uses a verb_adjective_noun structure. This inconsistency reduces predictability, though the names remain readable and descriptive.

Tool Count2/5

With only 3 tools, the server feels thin for a JIRA domain, which typically involves comprehensive issue and project management. This limited set is likely insufficient for common JIRA workflows, such as updating tasks, listing issues, or managing projects, suggesting an incomplete tool surface.

Completeness2/5

For a JIRA server, there are significant gaps in coverage: missing core operations like get_task, update_task, delete_task, list_issues, and manage_projects. The tools provided (create, search, set status) do not support a full CRUD lifecycle or common JIRA functionalities, leading to potential agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues