Huly MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 1 442 installs a week from npm. Last commit 31 Oct 2026.
Huly MCP: feature-complete MCP server for Huly integration
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const match = leadIdentifierPattern.exec(input.trim())
current = path.join(current, component)
{"encoding":"gzip-base64","data":"H4sIAAAAAAACE+y9+5LbyJEv/CoVPHZ0d5ikLmOf9XaH41hWa2Z6VxpppdY34R3L2mqi2MQKBGgU0C16VhHnIb4n/J7ki8ysKhRuJECy2bf0Hx41AdQ1K+uX919+HVymSb4YHA8WafLfapKdJ0mkB8NBLOdqcDyIQp19No/g50DpSRousjCJB8eD16HOhIwi8WMeLYV9bSzeqyxPY+1+ETpJMxWIi6WAdsfiQ75YJGmmxTSMMpWG8S…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add huly-mcp -e 'HULY_URL=<HULY_URL>' -e 'HULY_EMAIL=<HULY_EMAIL>' -e 'HULY_PASSWORD=<HULY_PASSWORD>' -e 'HULY_WORKSPACE=<HULY_WORKSPACE>' -- npx -y @firfi/huly-mcp{
"mcpServers": {
"huly-mcp": {
"command": "npx",
"args": [
"-y",
"@firfi/huly-mcp"
],
"env": {
"HULY_EMAIL": "<HULY_EMAIL>",
"HULY_PASSWORD": "<HULY_PASSWORD>",
"HULY_URL": "<HULY_URL>",
"HULY_WORKSPACE": "<HULY_WORKSPACE>"
}
}
}
}[mcp_servers.huly-mcp]
command = "npx"
args = ["-y", "@firfi/huly-mcp"]
env = { HULY_URL = "<HULY_URL>", HULY_EMAIL = "<HULY_EMAIL>", HULY_PASSWORD = "<HULY_PASSWORD>", HULY_WORKSPACE = "<HULY_WORKSPACE>" }{
"mcpServers": {
"huly-mcp": {
"command": "npx",
"args": [
"-y",
"@firfi/huly-mcp"
],
"env": {
"HULY_EMAIL": "<HULY_EMAIL>",
"HULY_PASSWORD": "<HULY_PASSWORD>",
"HULY_URL": "<HULY_URL>",
"HULY_WORKSPACE": "<HULY_WORKSPACE>"
}
}
}
}{
"servers": {
"huly-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@firfi/huly-mcp"
],
"env": {
"HULY_EMAIL": "<HULY_EMAIL>",
"HULY_PASSWORD": "<HULY_PASSWORD>",
"HULY_URL": "<HULY_URL>",
"HULY_WORKSPACE": "<HULY_WORKSPACE>"
}
}
}
}Put your own values in place of
<HULY_URL> (Reachable self-hosted or replacement hosted Huly API URL), <HULY_EMAIL> (Your Huly account email), <HULY_PASSWORD> (Your Huly account password), <HULY_WORKSPACE> (Huly workspace identifier).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
HULY_CONNECTION_TIMEOUT (Connection timeout in milliseconds. Omit to use the package default), HULY_TOOL_MODE (Tool exposure mode: auto (default), native, or proxy. Auto keeps exact claude-code native and resolves Codex, Cursor, Windsurf, Copilot, opencode, Claude AI, and unknown clients to proxy mode), PROXY_OUTPUT_STRICT (Set true to make active TOOLSETS / TOOLS a hard allow-list for proxy search, schema lookup, and invocation. Defaults to false), TOOLSETS (Comma-separated native Huly tool categories to expose, such as issues,projects,search. If unset with TOOLS, all native tools are exposed), TOOLS (Comma-separated exact native Huly tool names to expose in addition to selected TOOLSETS, such as list_documents,create_issue).
Alternatives to Huly MCP
same job, measured the same wayMCP server for monday.com integration.
MCP server for Azure API integration
MCP server for Hootsuite API integration
MCP server for Chanty API integration
MCP server for Harness API integration
MCP server for Xero API integration
MCP server for Zoho CRM API integration
MCP server for Rancher API integration
Huly MCP — questions
Answers built from our own checks of this server.