Summary

470 tools is more than a client can hold, so it does not send them.

Every tool definition costs context in every turn, whether or not it gets called, and 470 of them is not a surface any current client handles well. The choice here is deliberate and adapts to who is connecting: clients with their own tool search get the native list, everyone else gets four discovery tools and finds the rest at call time. TOOLSETS is the setting worth reaching for — pin the dozen tools you actually use as native, leave discovery for the long tail.

What it is

A feature-complete MCP server for Huly — issues, projects, documents, drives, HR, CRM and messaging. It covers 470 tools across 39 categories, which is more than most clients can hold, so by default it presents four discovery tools instead and dispatches the real ones behind them.

What you get

The default proxy surface: list_tool_categories to see what exists, search_tools to find the right one by keyword, get_tool_schema to read its parameters, and invoke_tool to run it
Claude Code sessions get the native tools directly, since that client does its own tool search; Codex, Cursor, Windsurf, Copilot, OpenCode and Claude Desktop get the proxy surface instead
HULY_TOOL_MODE=native makes every Huly tool first-class if your client can take it
TOOLSETS and TOOLS pin the tools you use constantly as native while leaving proxy discovery available for the rest — TOOLSETS=issues, or TOOLS=create_issue,fulltext_search
Issue and project work — create_issue, create_issue_from_template, create_issue_status, create_issue_template, create_milestone, create_component and create_label
Documents and knowledge — create_document, create_drawing, create_drive, create_drive_folder and create_access_link
Messaging and CRM — create_channel, create_direct_message, create_group_direct_message, create_lead and create_organization
Boards, inventory and schema customisation — create_board, create_board_card, create_card, create_event, create_huly_attribute, create_huly_enum and create_huly_permission
A Huly CLI built from the same operation registry, so the same operations are available as shell commands with matching inputs and outputs
get_huly_startup_diagnostic, which is what answers you when the runtime is wrong rather than failing silently

Requirements

A Huly instance — HULY_URL, HULY_EMAIL, HULY_PASSWORD and HULY_WORKSPACE. Node.js 22.19.0 or later, and this is the failure people hit: MCP clients do not supply a runtime, so npx resolves whatever Node is in the client's environment. On an older one the server comes up in a diagnostic-only mode that tells you which executable it found rather than pretending to work. Point the client at an absolute path to a compatible Node if needed. Note that hosted Huly is shutting down — the README points to the export and self-hosting guides; self-hosted deployments are unaffected.

Setup effort

One command plus a key — npx -y @firfi/huly-mcp@latest, then supply credentials