hh-jira

The hh-jira-mcp-server is an MCP server that integrates Jira access into the MCP ecosystem. It runs as a Python/uv-based server exposed via standard input/output, allowing you to query and manage Jira data through the MCP protocol and inspector tooling. With the configured environment variables, the server authenticates as a Jira user, targets a specific team, and applies a predefined Jira search filter to limit results to issues in the Development: In progress state. When running with the MCP Inspector, you can debug Live MCP traffic and inspect the messages exchanged between your client and the server at runtime.

Prerequisites:

• Python environment and uv (uv is the package runner for MCP servers)
• Access to a Jira instance and a Jira user with appropriate permissions
• keyring for storing credentials (optional but recommended)

Installation steps:

1. Install uv (if not already installed) per your system:
   • macOS (via Homebrew): uv install
   • Other platforms: follow uv installation instructions in the project docs
2. Install and configure keyring for password storage (optional):
   • Open a terminal and run: keyring set hh-jira-mcp-server v.pupkin
3. Prepare the server project files in your workspace (clone the MCP server repo if needed):
   • git clone <repository-url-for-hh-jira-mcp-server>
4. Build or install any required Python dependencies as dictated by the project (per uv guidance):
   • uv sync
   • uv build
5. Configure the MCP server using the provided configuration snippet (see Published Servers Configuration in the README) and place it in your MCP configuration location.
6. Run the server using the MCP launcher or uv directly with the appropriate command and environment variables as shown in the configuration.

Tips and common considerations:

• Environment variables control the Jira user, team, and the Jira search filter used by the server; ensure these reflect your Jira setup. Incorrect filters can return no results or cause errors.
• The MCP server communicates over stdio; debugging can be challenging. Use the MCP Inspector for a more convenient debugging surface.
• If you are developing locally, you can switch between Published (uvx) and Development (uv) configurations by adjusting the command and args in your mcpServers config.
• To store credentials securely, rely on the keyring integration and ensure your environment variables are kept secure in your deployment environment.
• When upgrading uv or the server, re-synchronize dependencies and rebuild as needed to avoid runtime issues.