Huly MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server | 3000 |
| HULY_URL | Yes | The URL of your Huly workspace (e.g., https://workspace.teasersoftware.com) | |
| HULY_EMAIL | Yes | Your Huly account email address | |
| HULY_PASSWORD | Yes | Your Huly account password | |
| HULY_WORKSPACE | Yes | The name of your Huly workspace |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_issueC | Create a new issue in Huly with correct fields |
| list_issuesC | List issues from Huly |
| list_projectsB | List all projects in Huly |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: create_issue handles creation, list_issues handles listing issues, and list_projects handles listing projects. There is no overlap or ambiguity between these three operations.
All tools follow a consistent verb_noun pattern with snake_case: create_issue, list_issues, list_projects. The naming is predictable and uniform throughout the set.
With only 3 tools, the set feels thin for a project management domain like Huly, lacking operations such as update_issue, delete_issue, or get_project. However, it covers basic listing and creation, making it borderline appropriate.
The tool surface is significantly incomplete for managing issues and projects. It includes create_issue and list_issues but misses update_issue and delete_issue, and list_projects lacks corresponding create_project, get_project, or update_project operations, leaving agents with dead ends.