Huly MCP: give coding agents a real handle on Huly.

Huly MCP is a TypeScript Model Context Protocol server for reading and changing Huly workspace state from the agent tools you already use.

Quick Start: Agent-guided setup

Hand this to your coding agent and let it configure Huly MCP in your local MCP client.

Read or select these instructions directly, or copy the complete text with the button above. 

Set up Huly MCP in my local MCP client.

Use the npm package @firfi/huly-mcp with:

command: npx
args: ["-y", "@firfi/huly-mcp@latest"]

Configure the MCP server with the name "huly".

Ask me for:
- HULY_URL for a reachable self-hosted or replacement hosted Huly instance
- HULY_WORKSPACE
- Either HULY_TOKEN, or HULY_EMAIL and HULY_PASSWORD

Warn me that hosted Huly at https://huly.app is shutting down, link the migration announcement at https://github.com/hcengineering/platform/blob/develop/README.md, and do not configure that hosted URL for a new installation.

Do not write Huly credentials into project files. Prefer user-level MCP configuration when credentials are involved, and do not expose secrets in chat, logs, or summaries.

After adding the server, tell me how to restart or reload my MCP client. Then verify the setup by calling get_huly_context and checking that the workspace, URL origin, transport, and auth mode look right without exposing secrets.

Prefer a Huly CLI?

Huly CLI is the feature-complete, terminal-native alternative to Huly MCP for shell scripts, command-line automation, and coding-agent workflows. It has full Huly operation parity with Huly MCP through native, schema-aware commands and structured JSON output.

Huly MCP and Huly CLI are maintained together in the same monorepo and derive from the same shared operation registry.

See Huly CLI examples, the automation guide, or a direct Huly MCP vs Huly CLI comparison.

Principles

Full Huly parity.

Expose the full useful Huly surface through MCP: projects, issues, documents, people, calendars, activity, files, processes, tests, and the rest.

LLM-friendly access.

Raw APIs are not enough. Tools need clear names, forgiving identifiers, rich results, useful errors, and enough context for an agent to take the next step.

Middleware for agents.

Huly MCP exists between Huly and coding agents: it translates Huly's workspace model into a tool surface agents can reason about and act through.

Tool Surface

Huly MCP exposes Huly workspace data and actions as MCP tools for agents that need to plan, inspect, update, and verify work without losing context.