Mannequin Context Protocol (MCP) servers present a brand new method to unify automation and observability throughout hybrid Cisco environments. They permit an AI consumer to mechanically uncover and use instruments throughout a number of Catalyst Heart clusters and Meraki organizations.
For those who’re interested in how this works, now’s the time to see it in motion.
On this new demo, Cisco Principal Technical Advertising and marketing Engineer Gabi Zapodeanu reveals how a single AI consumer routes natural-language queries to the precise software, retrieves responses from a number of domains, and helps you troubleshoot or report in your community extra effectively.
See MCP in Motion: Catalyst Heart and Meraki Integration
Within the video beneath, Gabi demonstrates how MCP servers allow an AI consumer to work together with instruments throughout a number of platforms. You’ll be taught:
- How the consumer connects to a number of MCP servers and discovers obtainable instruments.
- How these instruments are chosen and executed in actual time based mostly on consumer intent.
- How a single question can span clusters and organizations utilizing patterns like cluster = all.
The video contains sensible walkthroughs of multi-cluster stock lookups, situation correlation throughout, and a BGP troubleshooting workflow constructed from primary instruments.
Understanding MCP Structure and Workflow
MCP makes use of a client-server protocol that allows an AI assistant to hook up with a number of MCP servers and dynamically uncover obtainable software definitions. Here’s what the total workflow appears like:
- An AI consumer, powered by a big language mannequin, connects to a number of MCP servers.
- Every server gives an inventory of instruments—both prebuilt runbooks or auto-generated APIs.
- A consumer asks a query; the AI consumer selects the suitable software, fills within the parameters, and sends the request.
- The instruments execute, return information, and the AI responds to the consumer.
This permits asking a single query—equivalent to “The place is that this consumer linked?”—and receiving solutions from a number of clusters and organizations.
Crucial Instruments vs. Declarative Instruments in MCP Servers
The demo explains two sorts of instruments supported by MCP servers:
- Crucial instruments are predefined sequences written in Ansible, Terraform, or Python. They’re greatest suited to write duties the place guardrails and strict execution order are necessary.
- Declarative instruments are auto-generated from YAML information and are perfect for read-heavy duties equivalent to stock, occasion lookup, or compliance checks. Additionally they help pagination with offset and restrict parameters.
Gabi shares examples of each sorts, demonstrating their use in actual situations like firmware checks and cross-domain consumer discovery.
Troubleshooting and Compliance Utilizing Generative AI Flows
Past single-tool calls, MCP helps multi-step workflows. These generative AI flows allow you to:
- Correlate occasions
- Establish root causes of points equivalent to BGP flaps
- Run compliance checks or accumulate telemetry throughout websites
- Apply guardrails for adjustments, making certain solely trusted runbooks are used for configuration actions
The MCP consumer learns from software utilization patterns and might counsel new instruments based mostly on frequent API calls.
The best way to Get Began and What’s Subsequent
This demo gives a transparent, sensible introduction to MCP for anybody working in NetOps or DevOps. You’ll achieve a greater understanding of:
- Why MCP issues right now
- The best way to join MCP to your Cisco platforms
- The sorts of instruments and workflows it helps
- The best way to construction your individual instruments utilizing YAML or SDKs
Watch the total replay:
Subscribe to Cisco DevNet on YouTube to get notified when new demos go reside.