{
  "mcpServers": {
    "hh-jira-mcp-server": {
      "command": "uvx",
      "args": [
        "hh-jira-mcp-server"
      ],
      "env": {
        "HH_JIRA_MCP_USER": "v.pupkin",
        "HH_JIRA_MCP_TEAM": "some-team",
        "HH_JIRA_MCP_SEARCH_FILTER": "status in (\"Development: In progress\")"
      }
    }
  }
}

Configuración de servidores no publicados/desarrollo

{
  "mcpServers": {
    "hh-jira-mcp-server": {
      "command": "uv",
      "args": [
        "--directory",
        "<path_to_project>/hh-jira-mcp-server",
        "run",
        "hh-jira-mcp-server"
      ],
      "env": {
        "HH_JIRA_MCP_USER": "v.pupkin",
        "HH_JIRA_MCP_TEAM": "some-team",
        "HH_JIRA_MCP_SEARCH_FILTER": "status in (\"Development: In progress\")"
      }
    }
  }
}

Related MCP server: Jira MCP Server

Desarrollo

Construcción y publicación

Para preparar el paquete para su distribución:

Sincronizar dependencias y actualizar el archivo de bloqueo:

uv sync

Distribuciones de paquetes de compilación:

uv build

Esto creará distribuciones de origen y de rueda en el directorio dist/ .

Publicar en PyPI:

uv publish

Nota: Deberás configurar las credenciales de PyPI a través de variables de entorno o indicadores de comando:

Token: --token o UV_PUBLISH_TOKEN
O nombre de usuario/contraseña: --username / UV_PUBLISH_USERNAME y --password / UV_PUBLISH_PASSWORD

Depuración

Dado que los servidores MCP se ejecutan en stdio, la depuración puede ser complicada. Para una experiencia óptima, recomendamos usar el Inspector MCP .

Puede iniciar el Inspector MCP a través de npm con este comando:

npx @modelcontextprotocol/inspector uv --directory <path_to_project>/hh-jira-mcp-server run hh-jira-mcp-server

Al iniciarse, el Inspector mostrará una URL a la que podrá acceder en su navegador para comenzar a depurar.

Available Tools

3 tools

create_taskD

Name	Required	Description	Default
`title`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_team_active_portfoliosD

Name	Required	Description	Default
`team`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

set_defence_checkedD

Name	Required	Description	Default
`portfolio`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 18, 2025
- First observedcreate_task
- First observedsearch_team_active_portfolios
- First observedset_defence_checked

Deploy Server

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

TDQS

D1.6/5.0

Scored 2026-04-18 11:30 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 recent community issues

Resources

Related MCP Connectors

hithereiamaliff-mcp-nextcloud
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238
https://server.smithery.ai/@hithereiamaliff/mcp-nextcloud/mcp
Artificial Wit AI
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2
https://api.artificialwit.com/mcp
Airtable MCP by InsightfulPipeA
com.insightfulpipe
Hosted Airtable MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Databases Workplace & Productivity
41
https://airtable.insightfulmcp.com/
mcpC
com.wix
A Model Context Protocol server for Wix AI tools
Developer Tools Content Management Systems App Automation
215
https://mcp.wix.com/mcp

Related MCP Servers

JIRA MCP Tools
Project Management API Testing App Automation
NZenitram
F
license
Not graded
quality
D
maintenance
A Model Context Protocol (MCP) server that enables interaction with JIRA APIs through Claude Desktop, allowing users to search, create, update, and manage JIRA issues using natural language commands.
Updated 2 years ago (2025-03-21 15:01 UTC)
1
-
Jira MCP Server
App Automation Project Management
samuelrizzo
A
license
A
quality
D
maintenance
A Model Context Protocol server that enables AI assistants like Claude to interact with Jira, allowing for project management tasks such as listing projects, searching issues, creating tickets, and managing sprints through natural language queries.
Updated a year ago (2025-08-06 19:07 UTC)
7
1,383 npm
2
TypeScript
MIT
Jira MCP Server
Project Management App Automation
InfinitIQ-Tech
A
license
A
quality
F
maintenance
A Model Context Protocol server that enables interaction with Jira's REST API using natural language commands, allowing users to manage Jira projects, issues, comments, and workflows through Claude Desktop and other MCP clients.
Updated a month ago (2026-09-29 22:33 UTC)
10
7
MIT
Jira MCP Server
sespinosa
A
license
C
quality
D
maintenance
A Model Context Protocol server that enables AI assistants like Claude to interact with Jira Cloud instances, providing capabilities for issue management, project listing, and JQL search.
Updated a year ago (2025-07-07 21:36 UTC)
1
1,383 npm
2
MIT

hh-jira-mcp-server Servidor MCP

Inicio rápido

Instalar

Almacenar contraseña para cuenta jira

Escritorio de Claude

Desarrollo

Construcción y publicación

Depuración

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches