yzd098776/dsh-HCL-mcp

An MCP server that lets DSH plan H3C Cloud Lab topologies offline and inspect a running lab through its telnet bridge, with writes gated by receipts.

Two modes against the same model. Offline, a declarative request becomes a real staged HCL project — topologies you can inspect and adjust before anything runs. Live, the plugin reads the running lab through its own telnet bridge instead of scraping a UI. Device configuration changes only happen through gated, receipt-backed operations: destructive tools refuse the original HCL project, and read tools report a native_readback_verified flag so a claim about device state is backed by a read-back rather than an assumption. The README is explicit about what it does not do — it does not create HCL virtual machines or draw cables on the canvas — and it stores no credentials, leaving lab device logins inside HCL.

Tools & Capabilities ★ 3
View on GitHub ↗

Install

dsh plugin --profile desktop add dsh-mcp-hcl

The registry line from the README's Install section. This is one half of a two-part install: the MCP server itself is a Python package installed with pipx install mcp-hcl, and the plugin only registers the client-connector row that points DSH at it. The README also documents dsh plugin --profile desktop add . for a checkout.

Compatibility

Needs H3C Cloud Lab installed locally: the README says it talks only to 127.0.0.1:16600 (the HCL backend) and the lab's telnet bridge, and it was verified on a real Windows HCL install. Live writes are opt-in through MCP_HCL_ALLOW_LIVE_WRITE, which defaults to 0.

Details

Alternatives

zhe97396-tech/dsh-lazy-mcp · zhengjy01/dsh-feishu-mcp · kenny2077/dsh-web-kimi

More plugins in Tools & Capabilities

Browse more in Tools & Capabilities

Guides for Tools & Capabilities plugins