Choose Huly CLI
Use terminals, shell scripts, CI jobs, cron tasks, or coding agents that can execute subprocesses.
Explore Huly CLIOne operation registry · two interfaces
Huly MCP vs Huly CLI
Huly MCP and Huly CLI are maintained together and provide full parity across shared Huly operations. Choose the interface that fits how your human or agent works.
Quick decision
Choose Huly MCP
Let MCP-compatible agents discover Huly tools, inspect schemas, and invoke operations inside a conversation.
Set up Huly MCPFeature comparison
| Capability | Huly CLI | Huly MCP |
|---|---|---|
| Shared Huly operations | Full parity | Full parity |
| Primary interface | Native terminal commands | Model Context Protocol tools |
| Human-readable output | Yes | Agent-oriented tool results |
| Structured automation | --json, exit codes, files | Typed MCP inputs and results |
| Tool discovery | --help command tree | MCP discovery and proxy tools |
| Typical runtime | One command or script | Long-running stdio or HTTP server |
What parity means
Both packages derive their Huly-facing commands and tools from the same schema-owned operation registry. Operation inputs, results, warnings, and typed failures stay aligned as the project evolves.
Protocol mechanics are intentionally different. MCP resources, discovery, transports, and session behavior belong to Huly MCP; terminal help, output formatting, process exit codes, and file routing belong to Huly CLI.
You can use both
Use Huly MCP for conversational agent work and keep Huly CLI available for repeatable scripts, local diagnosis, or direct terminal use. Both packages use the same Huly connection settings.