@lazco-studio/huly-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HULY_URL | Yes | Base URL of your Huly instance, e.g. https://huly.example.com | |
| HULY_EMAIL | No | Account email — requires HULY_PASSWORD when not using a token. | |
| HULY_TOKEN | No | Auth token (recommended). Obtain from browser DevTools → Application → Local Storage. | |
| HULY_PASSWORD | No | Account password — requires HULY_EMAIL when not using a token. | |
| HULY_WORKSPACE | Yes | Workspace URL slug (not the display name) from the Huly URL | |
| HULY_TIMEOUT_MS | No | Connection timeout in milliseconds (default 30000 | 30000 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| huly_whoamiA | Verify the Huly connection and credentials, returning the current account and workspace. Run this first after configuring the server. |
| huly_list_teamspacesA | List all teamspaces (the spaces documents live in). You need a teamspaceId from here before creating a document. |
| huly_list_documentsA | List documents without their content. Filter by teamspaceId for a single space, or by parentId to get child documents. The returned ids can be passed to huly_get_document. |
| huly_get_documentA | Fetch a document title and its full content by ID (markdown by default). Content lives in a collaborative blob, so it can only be retrieved through this tool. |
| huly_search_documentsB | Search document titles by keyword. Set searchContent=true to also search document bodies (slower, since each document is fetched individually). |
| huly_create_documentA | Create a new document in a teamspace, with content supplied as markdown. Pass parentId to create it as a child document. |
| huly_update_documentA | Update a document title or content. content replaces the entire body; to append, first read the document with huly_get_document, merge, then write the result back. |
| huly_delete_documentA | Delete a document. This cannot be undone, so confirm the documentId is correct first. |
| huly_list_projectsA | List Tracker projects (the spaces issues live in). |
| huly_list_issuesA | List issues, optionally filtered by projectId. Results include the status name and the human identifier (e.g. PROJ-12). |
| huly_get_issueA | Fetch a full issue by internal ID or human identifier (e.g. PROJ-12), including its description and comments. |
| huly_comment_issueB | Add a comment to an issue. |
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 12 tools
Every tool pairs a clear verb with a distinct resource: teamspaces, documents, projects, issues, and the current user. list_documents and search_documents are differentiated by browsing vs. keyword search, and get_document vs. get_issue target completely different object types.
All tools use the huly_ prefix and follow a snake_case verb_noun pattern (list_, get_, create_, update_, delete_, search_, comment_). huly_whoami is the only slight outlier but is a conventional identity-check idiom and does not disrupt the overall consistency.
12 tools is well within the ideal scope for an integration server. The toolset covers two coherent resource families—documents and issues—with no redundant utilities or unnecessary bloat.
The document side has full lifecycle coverage (list, get, search, create, update, delete), but the issue side only supports list, get, and comment. Missing issue creation, update, deletion, and state transitions are significant gaps that prevent common issue-management workflows.