Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Huly MCP

by dearlordylordversion 0.56.0i★ 64iRuns on your computerOfficial site ↗
Registry nameio.github.dearlordylord/huly-mcp

How to install

What it does

Huly MCP: feature-complete MCP server for Huly integration

  • Connects Runs on your computer
  • Account or key Needs HULY_PASSWORD · 4 settings to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity28/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score40/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Huly MCP. Follow https://mcp.popnx.com/i/dearlordylord-huly-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Huly MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "huly": { "command": "npx", "args": [ "-y", "@firfi/huly-mcp" ], "env": { "MCP_TRANSPORT": "stdio-resident", "HULY_URL": "your-value", "HULY_EMAIL": "your-value", "HULY_PASSWORD": "your-value", "HULY_WORKSPACE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Huly MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Huly MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Huly MCP site ↗

  3. Fill in 4 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • MCP_TRANSPORT Local MCP runtime: resident shares a backend across compatible clients; stdio uses a separate backend per client. · default stdio-resident
    • HULY_URL Reachable self-hosted or replacement hosted Huly API URL
    • HULY_EMAIL Your Huly account email
    • HULY_WORKSPACE Huly workspace identifier

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "huly": {
          "command": "npx",
          "args": [
            "-y",
            "@firfi/huly-mcp"
          ],
          "env": {
            "MCP_TRANSPORT": "stdio-resident",
            "HULY_URL": "your-value",
            "HULY_EMAIL": "your-value",
            "HULY_PASSWORD": "your-value",
            "HULY_WORKSPACE": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Huly MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Huly MCP or shows a Huly MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Huly MCP yet

Huly MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Huly MCP

  • You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)
  • You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)
  • You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Huly MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user huly --env MCP_TRANSPORT=stdio-resident --env HULY_URL=your-value --env HULY_EMAIL=your-value --env HULY_PASSWORD=your-value --env HULY_WORKSPACE=your-value -- npx -y @firfi/huly-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Huly MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Huly MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Huly MCP site ↗

  3. Fill in 4 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • MCP_TRANSPORT Local MCP runtime: resident shares a backend across compatible clients; stdio uses a separate backend per client. · default stdio-resident
    • HULY_URL Reachable self-hosted or replacement hosted Huly API URL
    • HULY_EMAIL Your Huly account email
    • HULY_WORKSPACE Huly workspace identifier

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user huly --env MCP_TRANSPORT=stdio-resident --env HULY_URL=your-value --env HULY_EMAIL=your-value --env HULY_PASSWORD=your-value --env HULY_WORKSPACE=your-value -- npx -y @firfi/huly-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Huly MCP listed as connected

  7. Try it

    Use Huly MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Huly MCP or shows a Huly MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Huly MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "huly": { "command": "npx", "args": [ "-y", "@firfi/huly-mcp" ], "env": { "MCP_TRANSPORT": "stdio-resident", "HULY_URL": "your-value", "HULY_EMAIL": "your-value", "HULY_PASSWORD": "your-value", "HULY_WORKSPACE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Huly MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Huly MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Huly MCP site ↗

  3. Fill in 4 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • MCP_TRANSPORT Local MCP runtime: resident shares a backend across compatible clients; stdio uses a separate backend per client. · default stdio-resident
    • HULY_URL Reachable self-hosted or replacement hosted Huly API URL
    • HULY_EMAIL Your Huly account email
    • HULY_WORKSPACE Huly workspace identifier

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Huly MCP settings, HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Huly MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Huly MCP or shows a Huly MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Huly MCP key (create it on the maker’s site) · 4 setting(s) to fill in (MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Huly MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "huly": { "type": "stdio", "command": "npx", "args": [ "-y", "@firfi/huly-mcp" ], "env": { "MCP_TRANSPORT": "stdio-resident", "HULY_URL": "your-value", "HULY_EMAIL": "your-value", "HULY_PASSWORD": "your-value", "HULY_WORKSPACE": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Huly MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Huly MCP key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Huly MCP site ↗

  3. Fill in 4 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • MCP_TRANSPORT Local MCP runtime: resident shares a backend across compatible clients; stdio uses a separate backend per client. · default stdio-resident
    • HULY_URL Reachable self-hosted or replacement hosted Huly API URL
    • HULY_EMAIL Your Huly account email
    • HULY_WORKSPACE Huly workspace identifier

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Huly MCP settings, HULY_PASSWORD, MCP_TRANSPORT, HULY_URL, HULY_EMAIL, HULY_WORKSPACE is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Huly MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Huly MCP or shows a Huly MCP tool in the answer, you are connected

5 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • 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.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Huly MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user huly --env MCP_TRANSPORT=stdio-resident --env HULY_URL=your-value --env HULY_EMAIL=your-value --env HULY_PASSWORD=your-value --env HULY_WORKSPACE=your-value -- npx -y @firfi/huly-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "huly": {
      "command": "npx",
      "args": [
        "-y",
        "@firfi/huly-mcp"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio-resident",
        "HULY_URL": "your-value",
        "HULY_EMAIL": "your-value",
        "HULY_PASSWORD": "your-value",
        "HULY_WORKSPACE": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "huly": {
      "command": "npx",
      "args": [
        "-y",
        "@firfi/huly-mcp"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio-resident",
        "HULY_URL": "your-value",
        "HULY_EMAIL": "your-value",
        "HULY_PASSWORD": "your-value",
        "HULY_WORKSPACE": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "huly": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@firfi/huly-mcp"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio-resident",
        "HULY_URL": "your-value",
        "HULY_EMAIL": "your-value",
        "HULY_PASSWORD": "your-value",
        "HULY_WORKSPACE": "your-value"
      }
    }
  }
}

Values you fill in

  • MCP_TRANSPORT required env
    Local MCP runtime: resident shares a backend across compatible clients; stdio uses a separate backend per client.
  • HULY_URL required env
    Reachable self-hosted or replacement hosted Huly API URL
  • HULY_EMAIL required env
    Your Huly account email
  • HULY_PASSWORD secret required env
    Your Huly account password
  • HULY_WORKSPACE required env
    Huly workspace identifier
  • HULY_CONNECTION_TIMEOUT env
    Connection timeout in milliseconds. Omit to use the package default.
  • HULY_TOOL_MODE env
    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 env
    Set true to make active TOOLSETS / TOOLS a hard allow-list for proxy search, schema lookup, and invocation. Defaults to false.
  • TOOLSETS env
    Comma-separated native Huly tool categories to expose, such as issues,projects,search. If unset with TOOLS, all native tools are exposed.
  • TOOLS env
    Comma-separated exact native Huly tool names to expose in addition to selected TOOLSETS, such as list_documents,create_issue.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
637/wk
Connection
Runs on your computer
Latest versioni
0.56.0
Categoryi
Other
Published to registryi
Nov 11, 2026
Code last changedi
Nov 14, 2026
Maker
dearlordylord
Packages
npm: @firfi/huly-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account dearlordylord, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 5 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for @firfi/huly-mcp@0.56.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/dearlordylord-huly-mcp.svg)](https://mcp.popnx.com/en/servers/dearlordylord-huly-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 98% of the other 20693 servers in this category
  • Published to the registry more recently than 85% of the other 20693 servers in this category
  • Basic checks equal to or better than 99% of the other 20693 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Huly MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: HULY_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 5 days ago, and the latest version (0.56.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Huly MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Huly MCP

Huly MCP is a feature-complete MCP server for Huly integration. Published on npm as @firfi/huly-mcp.

It connects to Huly Platform deployments and should also work with the Platform Collective and TraceX forks. Intabia 0.8.33 / model 0.8.4 has been compatibility-tested; known gaps are tracked in issue #279. Fork support remains unofficial.

Huly CLI Alternative

Looking for a Huly CLI, terminal-native Huly integration, or a scripting and automation alternative to running an MCP server? Huly CLI is a feature-complete command-line interface for Huly, published as @firfi/huly-cli, with full Huly operation parity with Huly MCP. It exposes the same Huly operations as native, schema-aware commands with human-readable or JSON output, file-backed inputs, uploads, and downloads.

Huly MCP and Huly CLI are maintained together in this monorepo and derive from the same shared operation registry, keeping operation inputs, outputs, warnings, and typed failures aligned. See the Huly CLI documentation for the complete generated command reference, or browse CLI examples, Huly automation patterns, and the Huly MCP vs CLI comparison.

Installation

Node.js requirement

Huly MCP requires Node.js 22.19.0 or later. MCP clients do not provide a Node.js runtime: node, npx, and the #!/usr/bin/env node package executable resolve Node.js from the environment in which the MCP client runs. Check that environment before installation:

node --version

If an MCP client starts Huly MCP with an older runtime, Huly MCP initializes a diagnostic-only MCP surface instead of loading the incompatible application. Its server instructions and get_huly_startup_diagnostic tool report the detected executable and required version, and the same unsupported Node.js runtime diagnostic is written to stderr. Upgrade Node.js or configure the MCP server command to use the absolute path of a compatible Node.js executable, then restart the MCP server. Huly operations remain unavailable until the runtime is upgraded.

The standard configuration uses a Huly API token and works with most MCP clients:

{

"mcpServers": { "huly": { "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" } } } }

Prefer a managed API token created in Huly account settings when the target deployment supports it. Managed tokens are bound to one workspace, assigned an expiry, and can be revoked without changing the account password. They still inherit the account's full rights in that workspace, so use a dedicated integration account with only the workspace role, space memberships, and data access the automation needs. Older Huly deployments may not expose managed token settings; email/password authentication remains available as a compatibility fallback.

Tool Exposure Defaults

By default (HULY_TOOL_MODE=auto), Huly MCP optimizes for current MCP clients by avoiding a 470-tool eager list. Exact claude-code sessions receive native Huly tools. Codex, Cursor, Windsurf, Copilot, OpenCode, Claude AI/Desktop-style clients, and unknown clients receive a small proxy surface: list_tool_categories, search_tools, get_tool_schema, and invoke_tool.

Exact native tool names still dispatch when a client calls them directly, but many clients only call tools returned by tools/list. Set HULY_TOOL_MODE=native to make every Huly tool appear first-class, or use TOOLSETS / TOOLS to pin frequently used native tools while keeping proxy discovery available.

Codex

npx automatically downloads and caches Huly MCP; pnpm dlx @firfi/huly-mcp@latest is an alternative. Huly is optional, so Codex can start without it and a cold download may leave the first turn without Huly tools. Run /mcp to check the connection.

Add to ~/.codex/config.toml (the 120-second startup allowance includes installation):

[mcp_servers.huly]

startup_timeout_sec = 120 command = "npx" args = ["-y", "@firfi/huly-mcp@latest"]

[mcp_servers.huly.env] MCP_TRANSPORT = "stdio-resident" HULY_URL = "https://your-huly-instance.example.com" HULY_TOKEN = "your-huly-api-token" HULY_WORKSPACE = "yourworkspace"

Claude Code

claude mcp add huly \

-e MCP_TRANSPORT=stdio-resident \ -e HULY_URL=https://your-huly-instance.example.com \ -e HULY_TOKEN=your-huly-api-token \ -e HULY_WORKSPACE=yourworkspace \ -- npx -y @firfi/huly-mcp@latest

Or add to ~/.claude.json using the standard config above.

Claude Desktop

Add the standard config to your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

VS Code

Add with Command Palette → "MCP: Add Server", or put this in a VS Code MCP config such as .vscode/mcp.json. Do not commit workspace config files that contain real credentials.

{

"servers": { "huly": { "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" } } } }

Cursor

Add the standard config to ~/.cursor/mcp.json, or via Settings → Tools & Integrations → New MCP Server.

Windsurf

Add the standard config to your Windsurf MCP configuration file.

OpenCode

Open the global configuration file (~/.config/opencode/opencode.json) and merge this entry into your config:

{

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

Pi

Pi requires an MCP adapter. Install it, then use Huly MCP in auto mode with the four proxy tools promoted into Pi's native tool list:

pi install npm:pi-mcp-adapter

See the Pi setup guide for the user-global configuration, optional TOOLSETS/TOOLS native pins, and verification steps.

Updating

The @latest tag asks the package runner for the newest version. Some MCP clients keep server processes or resolved installs alive, so restart or re-add the server when updating:

ClientHow to update
Codexcodex mcp remove huly then re-add with the install command above. If your password has shell-sensitive characters, edit ~/.codex/config.toml directly instead
Claude Codeclaude mcp remove huly then re-add with the install command above
Claude DesktopRestart the app (it runs npx on startup)
VS Code / CursorRestart the MCP server from the command palette/configured client or reload the window
OpenCodeRestart OpenCode or start a new session after config changes
PiRun /mcp reconnect huly, then /reload if the registered direct-tool surface changed
npx (manual)MCP_TRANSPORT=stdio-resident npx -y @firfi/huly-mcp@latest — the -y flag auto-confirms install prompts

Maintainer Production Release

Publish from a clean, current master checkout with the preferred certified Node.js runtime:

mise exec node@24.15.0 -- pnpm local-release

Use this exact command even when a newer Node.js version is active on the host. The release build accepts only the exact Node.js versions certified by CI; this is intentionally narrower than the package's runtime requirement. See the production release guide for preflight checks, rerun behavior, and verification.

Shared resident stdio

The setup examples explicitly select MCP_TRANSPORT=stdio-resident. MCP clients still use stdio, while compatible clients under the same OS user share a Node backend through small native bridges. Linux and macOS arm64/x64 binaries are included; no Rust installation is needed. Application requests remain buffered during the 30-second resident startup budget. Startup failure launches ordinary stdio and dispatches the buffered application input once. A failed active resident never reconnects or replays application requests.

Omitting MCP_TRANSPORT still selects ordinary stdio, preserving existing installations. Set MCP_TRANSPORT=stdio explicitly to keep a separate backend per client. Restart the MCP client after changing the setting.

Manual resident backend

The experimental manual resident backend path lets independent stdio hosts select one explicitly started local backend through a private attachment file. Full qualification remains pending.

HTTP Transport

By default, the server uses stdio transport. For HTTP transport:

HULY_URL=https://your-huly-instance.example.com \

HULY_TOKEN=your-huly-api-token \ HULY_WORKSPACE=yourworkspace \ MCP_TRANSPORT=http \ npx -y @firfi/huly-mcp@latest

Server listens on http://127.0.0.1:3000/mcp by default.

Configure with MCP_HTTP_PORT and MCP_HTTP_HOST:

MCP_TRANSPORT=http MCP_HTTP_PORT=8080 MCP_HTTP_HOST=0.0.0.0 npx -y @firfi/huly-mcp@latest
HTTP MCP Protocol Support

Both transports are implemented with Effect AI's MCP server and protocol adapters. The server configures the released MCP 2026-07-28 stateless protocol and the MCP 2025-06-18 compatibility protocol. Modern HTTP requires one JSON-RPC message per POST, Accept: application/json, text/event-stream, MCP-Protocol-Version: 2026-07-28, Mcp-Method, method-specific Mcp-Name, and per-request _meta.io.modelcontextprotocol/* client metadata. Legacy HTTP supports initialized sessions using the returned Mcp-Session-Id and bare stateless calls with request-local bindings. Huly credentials are configured separately through env vars or supported x-huly-* headers.

See [MCP transport architecture and certification]

Only the beginning is shown; read the rest in the repo