Exposes Jira data through the Model Context Protocol.
Hh Jira MCP server exists for a simple reason — assistants are far more useful when they can act on Hh Jira directly instead of describing what you should do. Exposes Jira data through the Model Context Protocol.
Published Servers Configuration json { "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\")" } } } }
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Once Hh Jira is connected, these are the calls the assistant has available:
Token — --token or UV_PUBLISH_TOKENDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPYou will need 4 environment variables: HH_JIRA_MCP_USER, HH_JIRA_MCP_TEAM, HH_JIRA_MCP_SEARCH_FILTER, UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hh Jira's toolset — Token, Debugging — is a fair guide to whether it matches your workflow. It is maintained by alexeydubinin; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Token | --token or UV_PUBLISH_TOKEN |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
{
"mcpServers": {
"hh-jira": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"HH_JIRA_MCP_USER": "your-value",
"HH_JIRA_MCP_TEAM": "your-value",
"HH_JIRA_MCP_SEARCH_FILTER": "your-value",
"UV_PUBLISH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| HH_JIRA_MCP_USER | Configuration value read at startup. | Optional |
| HH_JIRA_MCP_TEAM | Configuration value read at startup. | Optional |
| HH_JIRA_MCP_SEARCH_FILTER | Configuration value read at startup. | Optional |
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.