# dearlordylord/huly-mcp [Health: Active]

**Category:** 📋 Product Management  
**Repository:** https://github.com/dearlordylord/huly-mcp  
**GitHub Stars:** 59  
**npm Downloads (last month):** 10814  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dearlordylord-huly-mcp

## Description
MCP server for Huly project management. Query issues, create and update tasks, manage labels and priorities.

## Tools
Capabilities this server exposes over MCP:

- **get_huly_startup_diagnostic** — Huly MCP startup failed: unsupported Node.js runtime. Detected 20.9.0 at /usr/local/bin/node; required >=22.19.0. MCP hosts use the Node.js executable resolved by their configured command and PATH. Install Node.js 22.19.0 or later, or configure this MCP server's command to a compatible Node.js executable, then restart the MCP server.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "huly-mcp": {
    "command": "npx",
    "args": ["-y","@firfi/huly-mcp@latest"],
    "env": {
      "MCP_TRANSPORT": "",
      "HULY_URL": "",
      "HULY_TOKEN": "",
      "HULY_WORKSPACE": ""
    }
  }
}
```

**Requires environment variables:** `MCP_TRANSPORT`, `HULY_URL`, `HULY_TOKEN`, `HULY_WORKSPACE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What dearlordylord/huly-mcp does

dearlordylord/huly-mcp exposes Huly project-management operations through the Model Context Protocol. Agents can query issues, create and update tasks, and manage labels and priorities. The package is published as `@firfi/huly-mcp` and connects to Huly Platform deployments using the Huly API.

The server is also intended to work with the Platform Collective and TraceX forks. Fork support is unofficial. Intabia compatibility has been tested for the versions identified by the project, while known compatibility gaps are tracked separately by the maintainers.

## How it works

The usual deployment runs as a local stdio MCP process started with `npx`. Huly connection details are supplied as environment variables, and the server uses those credentials to perform operations in a selected workspace.

Tool discovery defaults to `HULY_TOOL_MODE=auto`. In this mode, the server avoids eagerly listing hundreds of Huly tools. Clients that receive native tools can use the Huly operations directly; other clients receive a smaller discovery surface consisting of category listing, tool search, schema retrieval, and tool invocation. Setting `HULY_TOOL_MODE=native` exposes the Huly tools as first-class tools. Frequently used tools can also be selected with `TOOLSETS` or `TOOLS`.

## Setup and configuration

Node.js 22.19.0 or newer must be available to the MCP client process. The client resolves `node`, `npx`, and the package executable from its own environment, so upgrading Node.js in a separate shell may not fix a client that uses a different PATH. If an older runtime is detected, the server starts only a diagnostic MCP surface and reports the problem through `get_huly_startup_diagnostic` and stderr.

A standard configuration uses the package runner and these values:

```json
{
  "command": "npx",
  "args": ["-y", "@firfi/huly-mcp@latest"],
  "env": {
    "MCP_TRANSPORT": "stdio-resident",
    "HULY_URL": "https://your-huly-instance.example.com",
    "HULY_TOKEN": "your-huly-api-token",
    "HULY_WORKSPACE": "yourworkspace"
  }
}
```

Managed Huly API tokens are preferred where the deployment supports them. They are tied to one workspace, can expire, and can be revoked independently of the account password. A dedicated integration account with only the required workspace permissions limits the effect of the token. Older Huly deployments may require email and password authentication instead.

## Tools and capabilities

The exposed Huly operations cover:

- Querying issues
- Creating tasks
- Updating tasks
- Managing labels
- Managing priorities
- Discovering available tool categories
- Searching for tools and retrieving their schemas
- Invoking tools through the proxy surface
- Reporting an unsupported Node.js startup runtime

Native exposure and proxy discovery vary according to the client and `HULY_TOOL_MODE` setting. Exact native tool names can still be dispatched directly even when a client receives the smaller proxy list.

## Limitations and notes

Huly operations are unavailable until the Node.js runtime requirement is satisfied. Some clients retain a running server process or cached package installation, so configuration and package updates may require restarting or re-adding the MCP server.

Fork compatibility is unofficial, and Huly account permissions still apply to every operation performed with the configured credentials. Codex may need additional startup time for the initial `npx` download; its configuration example allows 120 seconds for startup.

_Full upstream README: https://allmcps.com/mcp/dearlordylord-huly-mcp/readme_