huly-mcp / site

# Huly MCP

Huly MCP is the maintained Huly Model Context Protocol server for coding agents that need serious, context-rich access to Huly workspaces.

It is built as LLM-friendly middleware between Huly and MCP-compatible agents. The project focuses on full Huly parity, useful tool names, forgiving identifiers, rich results, actionable errors, and enough workspace context for agents to continue work without guessing.

Use Huly MCP when an agent needs to inspect, plan, update, or verify work in Huly through programmatic tools.

## Canonical Links

- Website: https://huly-mcp.dearlordylord.com/
- Huly: https://huly.io/
- Source repository: https://github.com/dearlordylord/huly-mcp
- npm package: https://www.npmjs.com/package/@firfi/huly-mcp
- Huly CLI website: https://huly-mcp.dearlordylord.com/cli/
- Huly CLI examples: https://huly-mcp.dearlordylord.com/cli/examples/
- Huly CLI automation guide: https://huly-mcp.dearlordylord.com/cli/automation/
- Huly MCP vs Huly CLI: https://huly-mcp.dearlordylord.com/cli/huly-mcp-vs-cli/
- Huly CLI npm package: https://www.npmjs.com/package/@firfi/huly-cli
- Huly CLI documentation: https://github.com/dearlordylord/huly-mcp/tree/master/packages/huly-cli

## Positioning

- The maintained Huly MCP server for agent workflows.
- Full Huly parity through MCP tools.
- LLM-friendly, context-rich programmatic access to Huly workspace state.
- Middleware between Huly and coding agents.
- Huly CLI is the jointly maintained, terminal-native alternative for shell scripts, command-line automation, and coding-agent workflows.
- Huly MCP and Huly CLI have full shared-operation parity through the same schema-owned operation registry.

## Huly CLI

Huly CLI is the feature-complete command-line interface for Huly. It provides 500+ native commands for projects, issues, documents, chat, calendar, files, business workflows, and workspace administration.

Use Huly CLI for interactive terminal work, shell scripts, CI jobs, cron tasks, and coding agents that execute subprocesses. It supports human-readable output, structured JSON, file-backed inputs, uploads, downloads, typed failures, and explicit confirmation for consequential operations.

Use Huly MCP instead when an MCP-compatible agent should discover and invoke Huly tools through Model Context Protocol. Protocol mechanics differ, while shared Huly operations remain aligned.

## Quick Start: Agent-Guided Setup

Give the following instructions to a coding agent:

```text
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


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.
```

## 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.

Current tool areas include projects, issues, comments, milestones, documents, storage, attachments, contacts, channels, calendar, time tracking, search, associations, activity, notifications, workspace, approvals, boards, cards, collaborators, custom fields, Drive, inventory, labels, leads, mail, templates, model administration, Planner, preferences, processes, recruiting, SDK discovery, security administration, sequence administration, spaces, support, tag categories, tags, task management, test management, user statuses, views, virtual office, Workbench, and workflow statuses.

## Agent Notes

- Prefer user-level MCP configuration when credentials are involved.
- Never write Huly credentials or local MCP secrets into project files.
- Verify configuration with `get_huly_context` after setup.
- Do not expose tokens, passwords, or sensitive workspace values in logs or summaries.