Huly MCP: Huly issues and documents for an agent
Huly MCP
An MCP server for the Huly platform: issues, projects, documents, calendar and dozens more areas, plus the same set as a CLI
- 64 ★ on the repository
- Last commit
Broad access
Why this level
- The token inherits account rights and allows creating, changing and permanently deleting issues, projects and documents
- Contents of issues and documents reach the agent context and may carry instructions from others
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/huly-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The token inherits account rights and allows creating, changing and permanently deleting issues, projects and documents
- Contents of issues and documents reach the agent context and may carry instructions from others
This is third-party code. Review the repository files before installing.
What it does
The server connects to a Huly platform deployment by URL, workspace and API token and opens about 470 operations to the agent. They are grouped by area: projects, issues, comments, milestones, documents, attachments, contacts, channels, calendar, time tracking, search, notifications, HR, recruiting, support and more. The repository claims compatibility with Platform Collective and TraceX forks, and Intabia is partially verified. To avoid loading hundreds of tools into context, the HULY_TOOL_MODE setting picks by client. Claude Code gets native tools, while Codex, Cursor, Windsurf, Copilot, OpenCode and Claude Desktop get four proxy tools: list_tool_categories, search_tools, get_tool_schema and invoke_tool. The TOOLSETS and TOOLS variables pin the tools you use often. Transports are stdio and HTTP, with diagnostic tools get_huly_context and get_huly_startup_diagnostic and read-only resources. The same repository holds a Huly CLI built on a shared operation registry.
Who it is for. Teams that run their work in Huly and want an agent to create issues, read documents and change statuses without manual clicks.
Good fit when
- The agent should create a batch of issues in a project from planning text
- You want issues found by labels and milestone and a sprint status summary
- Project documents and attachments need reading and retelling for the team
- You want routine Huly operations in scripts through a CLI with the same operations
- Before deleting an entity you want to check the impact with preview_deletion
Not a fit when
- You do not use Huly: the server works only with its deployment and a token
- The task needs a couple of tools: 470 operations are overkill, pin a minimum through TOOLS
- The agent must not change or delete data: the token inherits the account rights in the workspace
Example request
Find all open issues in the Backend project with the bug label and the Q4 milestone, group them by assignee and show a summary.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
HULY_URLrequired- Huly deployment URL
HULY_TOKENrequired, secret- Huly API token, preferably managed and time-limited
HULY_WORKSPACErequired- Huly workspace name
HULY_TOOL_MODE- Tool exposure mode: auto, native or proxy
Limitations
Node.js 22.19.0 or newer is required: on an older version the server starts in diagnostic mode and only reports the runtime. A managed API token is bound to one workspace and has an expiry but inherits all account rights, so create a dedicated agent account with minimal roles. Older Huly deployments may not issue managed tokens, which leaves email and password login. Some clients only call tools listed in tools/list, so in proxy mode pinning through TOOLSETS helps. Intabia compatibility is partially verified.
How to disable. Run claude mcp remove huly and revoke the API token in Huly account settings. Delete the dedicated agent account if you created one for the integration.
FAQ
How many tools does the server have?
About 470 operations across dozens of areas. To avoid overloading context, auto mode shows Claude Code all native tools and gives other clients four proxy tools for search and invocation.
How do I pin the tools I need?
List areas in TOOLSETS or exact names in TOOLS separated by commas, or set HULY_TOOL_MODE=native to make every tool native. Proxy discovery remains available.
Which token should I use?
A managed API token from Huly account settings is preferred: it is bound to a workspace, has an expiry and can be revoked without changing the password. Email and password login remains a fallback.
Does it run over HTTP?
Yes, besides stdio there is an HTTP mode with MCP protocol support, shared stdio profiles and header configuration for a hosted server. See the HTTP Transport section of the README.
Is there a CLI instead of MCP?
Yes, the same repository holds the Huly CLI, the @firfi/huly-cli package. It is built on the same operation registry, so inputs and outputs match MCP.
Discussion
No questions or reviews yet.
Related
MCP serversHycli turns a website URL and a goal into a typed CLI and MCP tools that run in your own browser session, with no cookie leaks.
The Apideck MCP server: an agent works with over 200 business systems: accounting, HRIS, CRM and files through one unified API
MCP server where an agent asks a human questions and waits for answers, which arrive through MCP tools or an HTTP API.
An MCP server for a personal news pipeline: fetch, score, filter and summarize news through tools an agent can call
A self-hosted task board for people and agents: agents claim cards over MCP, and the receipt log cannot be rewritten.
A self-hosted control plane for running several agents: task dispatch, run review, spend tracking, connected via MCP, CLI or REST
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Huly MCP: Huly issues and documents for an agent (this card) | no | API key | 64 | |
| Linear MCP Server | no | API key | 346 | an MCP for the Linear tracker, does not touch the Huly platform |
| Jira MCP | no | key is optional | 96 | an MCP for Jira, a different tracker and data model |
README in short
The README covers installation for Claude Code, Codex, Cursor, Windsurf, Pi and other clients, tool exposure modes, environment variables, stdio and HTTP transports, diagnostics and resources. An auto-generated tool catalog by area closes it.