Huly MCP vs VoteShip
A side-by-side look at the Huly MCP and VoteShip 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 VoteShip for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Huly MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HULY_URL, HULY_TOKEN, HULY_WORKSPACE. - You want tools like
get_huly_startup_diagnostic.
Choose VoteShip when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 68/100 · Great | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | HULY_URLHULY_TOKENHULY_WORKSPACE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 59 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Huly MCP | View VoteShip |
Tools & capabilities
Huly MCP tools 1
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.
VoteShip tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Huly MCP
{
"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"
}
}
}
}
VoteShip
{
"mcpServers": {
"voteship-2": {
"command": "npx",
"args": [
"-y",
"@voteship/cli"
]
}
}
}
Frequently asked questions
Huly MCP is categorized under Product Management and uses a local stdio subprocess. VoteShip belongs to Product Management and uses a local stdio subprocess. Pick Huly MCP for product management work and VoteShip for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Huly MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. VoteShip is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add dearlordylord-huly-mcp and voteship-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Huly MCP has a quality signal of 68/100 (Great) with 5 views, 0 installs and 59 GitHub stars. VoteShip has 43/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.