Summary
The team is configuration rather than an argument, so a session is bound to one team before the first call.
The search filter is fixed the same way, which makes this one team's workflow expressed as three tools rather than a general Jira client. What is exposed matches that: portfolios, a defence-checked flag, and a task created from a title alone — no issue transitions, no boards, no comments, and no field on create_task other than the title.
What it is
A narrow Jira client bound to a single team: its active portfolios, a defence-checked flag on one of them, and task creation.
What you get
- search_team_active_portfolios, which returns the active portfolios for a named team.
- set_defence_checked, which marks a named portfolio as defence-checked.
- create_task, which creates a task from a title.
Requirements
HH_JIRA_MCP_USER, HH_JIRA_MCP_TEAM and HH_JIRA_MCP_SEARCH_FILTER — a Jira user, the team the server is bound to, and a search filter — plus the Jira instance they authenticate against.
Setup effort
One command plus a key — uvx hh-jira-mcp-server, then supply credentials