A side-by-side look at the Huly MCP and Linear Bootstrap MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Huly MCP for product management work as a local process; choose Linear Bootstrap for product management. You can also run both side by side in one mcpServers block.
HULY_URL, HULY_TOKEN, HULY_WORKSPACE.get_huly_startup_diagnostic.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 61/100 · Good | 29/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | HULY_URLHULY_TOKENHULY_WORKSPACE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 58 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Huly MCP | View Linear Bootstrap |
get_huly_startup_diagnosticHuly 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.No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"dearlordylord-huly-mcp": {
"command": "npx",
"args": [
"-y",
"@firfi/huly-mcp@latest"
],
"env": {
"HULY_URL": "YOUR_HULY_URL_HERE",
"HULY_TOKEN": "YOUR_HULY_TOKEN_HERE",
"HULY_WORKSPACE": "YOUR_HULY_WORKSPACE_HERE"
}
}
}
}
No confirmed install command for Linear Bootstrap yet — follow the setup steps linked from its listing page rather than a guessed package name.
