Summary
Consider exposing reference network topologies (Cisco SDA, campus 3-tier, DC spine-leaf, branch SD-WAN, …) as MCP resources so an LLM connected to cml-mcp can build well-known designs without the user having to describe them from scratch.
Motivation
Today the server exposes 51 tools that operate on CML, but no design knowledge. Asking an assistant to "build a basic Cisco SDA lab" requires the user to supply the topology, addressing plan, and node roles. That knowledge is largely fixed and reusable, and the MCP server is the natural place to ship it — versioned, curated, and known to work with the existing tools (create_full_lab_topology, connect_two_nodes, configure_cml_node, …).
Proposal
Expose templates as MCP resources with URI templates:
cml://templates # index
cml://templates/{family}/{name} # e.g. cml://templates/sda/basic
Each resource returns a Markdown document with the topology YAML, node roles, addressing plan, and design notes. Templates live in-repo (e.g. src/cml_mcp/templates/) and are reviewed via PR.
fastmcp>=3.1.1 already supports resources and resource templates, so this is purely additive — no changes to the existing 51 tools.
Offer to contribute
If maintainers are open to this, I'm happy to work on an initial PR with one template (sda/basic).
Summary
Consider exposing reference network topologies (Cisco SDA, campus 3-tier, DC spine-leaf, branch SD-WAN, …) as MCP resources so an LLM connected to
cml-mcpcan build well-known designs without the user having to describe them from scratch.Motivation
Today the server exposes 51 tools that operate on CML, but no design knowledge. Asking an assistant to "build a basic Cisco SDA lab" requires the user to supply the topology, addressing plan, and node roles. That knowledge is largely fixed and reusable, and the MCP server is the natural place to ship it — versioned, curated, and known to work with the existing tools (
create_full_lab_topology,connect_two_nodes,configure_cml_node, …).Proposal
Expose templates as MCP resources with URI templates:
Each resource returns a Markdown document with the topology YAML, node roles, addressing plan, and design notes. Templates live in-repo (e.g.
src/cml_mcp/templates/) and are reviewed via PR.fastmcp>=3.1.1already supports resources and resource templates, so this is purely additive — no changes to the existing 51 tools.Offer to contribute
If maintainers are open to this, I'm happy to work on an initial PR with one template (
sda/basic).