- Home
- MCP servers
- hh-jira
hh-jira
- python
2
GitHub Stars
python
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"alexeydubinin-hh-jira-mcp-server": {
"command": "uvx",
"args": [
"hh-jira-mcp-server"
],
"env": {
"HH_JIRA_MCP_TEAM": "some-team",
"HH_JIRA_MCP_USER": "v.pupkin",
"HH_JIRA_MCP_SEARCH_FILTER": "status in (\"Development: In progress\")"
}
}
}
}You run an MCP server that connects your Jira data to an MCP client, enabling real-time queries and automation across your Jira projects. This guide walks you through how to use, install, and configure the hh-jira-mcp-server for development and production workflows.
How to use
Start by choosing how you want to run the server. For a quick, production-like setup, use the published server configuration which runs the MCP server through the runtime frontend. For development, use the local runtime with your project directory so you can iterate on code and configurations.
How to install
Prerequisites: you need the MCP runtime tool and a compatible shell. The server runs as a stdio process started by the MCP runtime.
- Install the MCP runtime (uv) on your system. On macOS with Homebrew you can install it with:
brew install uv
- If you plan to store credentials securely for Jira access, you can store the Jira account password for your MCP server in your keyring. The example stores a password for the user v.pupkin under the hh-jira-mcp-server entry:
keyring set hh-jira-mcp-server v.pupkin
- Prepare the server configuration for either a published (production-like) setup or a development setup as shown in the examples below.
Configuration examples
Use these JSON snippets to configure how the MCP server runs under the MCP runtime. The published configuration is intended for a deployed, stable setup, while the development configuration is for local development.
{
"mcpServers": {
"hh-jira_mcp": {
"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\")"
}
}
}
}
{
"mcpServers": {
"hh-jira_mcp": {
"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\")"
}
}
}
}
Notes on security and usage
The server runs over standard input/output. Keep your Jira credentials secure and rotate them as needed using the password manager where you store them. When debugging, use the MCP Inspector tool to observe the runtime behavior and diagnose issues in real time.
Troubleshooting
If you encounter startup issues, verify that the MCP runtime (uv or uvx) is installed and that the environment variables you configured are accessible to the process. Use the MCP Inspector to attach a debugging session and monitor the start sequence and I/O you receive from Jira.
Available tools
MCP Inspector
Debugger to inspect MCP server runtime I/O and interactions; provides a UI to attach to the MCP process and view traffic.