Network Sketcherofficial
A
licenseA
qualityA
maintenanceLocal-first MCP server that lets AI agents design Cisco-style networks and generate L1/L2/L3 topology diagrams, device tables, and AI-ready context files.
18
12
413
Apache 2.0
MCP_HCL
by yzd098776
Related Servers
Alternatives to MCP_HCL
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server for managing home lab VMs and PNETLab topologies, enabling AI agents to power VMs, handle snapshots, and verify device configurations with explicit allowlists and confirmation gating.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control the H3C HCL network simulator through MCP, including creating topologies, adding/starting devices, wiring links, reading console output, and running CLI commands.MIT
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that wraps DeepSeek Harness's local /api into 9 tools, letting any standard MCP client create or adopt named dsh sessions, dispatch task briefs, poll asynchronously, and retrieve auditable per-turn results. It also enforces pre-validated model allowlists, workspace/alias boundaries, and a persistent session ledger, so agents can collaborate across harnesses without modifying dsh or installing client plugins.331 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that allows LLMs to create, configure, validate, and explain Cisco Packet Tracer network topologies. It provides a comprehensive suite of tools for generating deployment scripts, CLI configurations, and automated network troubleshooting.841 PyPI325MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with local H3C Cloud Lab network simulation environments, allowing discovery of projects, devices, and links, as well as execution of Comware CLI commands.1Apache 2.0
TDQS
C2.6/5.0
Scored across 55 tools
Disambiguation3/5
Many tools target distinct phases, but several clusters overlap: hcl_capabilities/hcl_backend_capabilities/hcl_parity_report/hcl_bridge_status; hcl_stage_copy/hcl_full_build/hcl_stage_plan; hcl_plan_topology/hcl_estimate_plan; and hcl_apply_vlan/hcl_apply_vlan_network. hcl_stage_add_device can also link, overlapping with hcl_stage_link. Descriptions help, but the set is large enough that an agent could easily misselect.
Naming Consistency4/5
All tool names use a consistent hcl_ prefix and snake_case, with most following a verb_noun pattern such as hcl_list_devices, hcl_stage_add_device, and hcl_apply_vlan. Minor deviations like hcl_capabilities, hcl_full_build, hcl_device_power, and hcl_console_exec are still readable and do not seriously break the pattern.
Tool Count1/5
With 55 tools, the surface is far beyond a well-scoped 3-15 range and even beyond the 25+ threshold for 'too many'. The many specialized, gated, and stage-specific operations make the server unwieldy for an agent to navigate reliably.
Completeness4/5
The tool set broadly covers planning, validation, staging CRUD, project lifecycle, config generation/export/load, backup/restore/deploy, live readback, audit, and many apply/remove operations. Some gaps remain, such as project deletion and complete live link inventory, and power-off is unsupported, but the core lifecycle is well represented.
Maintenance
ActivityMaintained
ResponsivenessNo issues