Huly MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HULY_URL | Yes | Huly instance URL (must be valid http or https URL) | |
| LAZY_ENVS | No | Defer client connection until first tool call ("true" or "false", default: "false") | |
| HULY_EMAIL | No | Email for password auth (required if HULY_TOKEN not set) | |
| HULY_TOKEN | No | Auth token (alternative to email/password) | |
| HULY_PASSWORD | No | Password for password auth (required if HULY_TOKEN not set) | |
| HULY_WORKSPACE | Yes | Workspace identifier | |
| HULY_CONNECTION_TIMEOUT | No | Connection timeout in ms (positive integer, default: 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
} |
| logging | {} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_versionA | Returns the current version of this Huly MCP server and the latest version available on npm. |
| get_huly_contextA | Returns sanitized runtime and configuration context for this Huly MCP session, including package version, transport, auth mode, Huly URL origin/host, workspace, timeout, native tool scope filtering, and resolved native/proxy tool exposure. Does not connect to Huly. Secret values such as tokens, passwords, and credential headers are never returned. |
| list_tool_categoriesA | Lists Huly tool categories available through this proxy. Use this first when you need a broad map of capabilities before searching for a specific Huly tool. |
| search_toolsA | Searches the current proxy-visible Huly tool catalog by tool name, category, description, and parameter names. Returns exact tool names plus required and optional parameter names for single-call follow-up with get_tool_schema or invoke_tool. |
| get_tool_schemaA | Returns the exact input and output schema for one proxy-visible Huly tool. Use this before invoke_tool when you are not certain about required argument names or result shape. |
| invoke_toolA | Invokes one proxy-visible Huly tool by exact name with its arguments. This tool can call read or write Huly operations; check get_tool_schema and the target tool annotations when safety matters. |
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 6 tools
Each tool has a distinct role: version, context, catalog search, category listing, schema lookup, and invocation. The only mild overlap is between get_version and get_huly_context, since the latter already reports package version, but they otherwise serve clearly separate purposes.
All six tools use consistent snake_case with a predictable verb_noun pattern (get_version, get_huly_context, search_tools, list_tool_categories, get_tool_schema, invoke_tool). Naming is fully coherent and self-explanatory.
Six tools is well-scoped for a proxy/meta server, covering discovery, inspection, and invocation without bloat. Each tool earns its place in the discovery-to-invocation workflow.
The proxy surface covers the full lifecycle: list categories, search tools, inspect schema, and invoke, plus version and context diagnostics. No obvious missing operations for a tool-catalog proxy.