Huly MCP: feature-complete MCP server for Huly integration
Most developer tooling work still happens through a UI a human drives. Huly MCP MCP server moves it into the conversation instead. Huly MCP: feature-complete MCP server for Huly integration.
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.
The server publishes 6 tools. What each one is for:
list_tool_categories — Lists Huly tool categories available through this proxy. Use this first when you need a broad map of capabilities before searching for a specificsearch_tools — Searches the current proxy-visible Huly tool catalog by tool name, category, description, and parameter names. Returns exact tool names plus requiredget_tool_schema — Returns the exact input and output schema for one proxy-visible Huly tool. Use this before invoke_tool when you are not certain about requiredinvoke_tool — Invokes one proxy-visible Huly tool by exact name with its arguments. This tool can call read or write Huly operations; check get_tool_schema and theProjects — The Projects tool exposed by this serverIssues — The Issues tool exposed by this serverConfiguration is passed through the environment: HULY_URL, HULY_EMAIL, HULY_PASSWORD, HULY_WORKSPACE, MCP_HTTP_HOST, MCP_AUTH_TOKEN, HULY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Huly MCP's toolset — list_tool_categories, search_tools, get_tool_schema and 3 more — is a fair guide to whether it matches your workflow. It is maintained by dearlordylord; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| list_tool_categories | Lists Huly tool categories available through this proxy. Use this first when you need a broad map of capabilities before searching for a specific Huly tool. |
| search_tools | Searches the current proxy-visible Huly tool catalog by tool name, category, description, and parameter names. Returns exact tool names plus required and optional parameter names for single-call follow-up with get_tool_s |
| get_tool_schema | Returns the exact input and output schema for one proxy-visible Huly tool. Use this before invoke_tool when you are not certain about required argument names or result shape. |
| invoke_tool | Invokes one proxy-visible Huly tool by exact name with its arguments. This tool can call read or write Huly operations; check get_tool_schema and the target tool annotations when safety matters. |
| Projects | The Projects tool exposed by this server. |
| Issues | The Issues tool exposed by this server. |
{
"mcpServers": {
"huly": {
"command": "npx",
"args": ["-y", "@firfi/huly-mcp@latest"],
"env": {
"HULY_URL": "https://your-huly-instance.example.com",
"HULY_EMAIL": "your@email.com",
"HULY_PASSWORD": "yourpassword",
"HULY_WORKSPACE": "yourworkspace"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HULY_URL | Endpoint or connection string the server talks to. | Yes |
| HULY_EMAIL | Configuration value read at startup. | Optional |
| HULY_PASSWORD | Configuration value read at startup. | Optional |
| HULY_WORKSPACE | Configuration value read at startup. | Optional |
| MCP_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
| MCP_AUTH_TOKEN | Credential the server authenticates with. | Yes |
| HULY_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.