network_platforms_mcp_servers

This MCP server collection demonstrates learning, development, and orchestration of Meraki and Catalyst Center APIs using the Model Context Protocol. The Basic Meraki MCP Server provides a minimal, single-tool example to register a tool (list_organizations_details) with one API key and no input parameters, ideal for understanding server structure and tool registration. The Foundation and Multi-Org Meraki servers extend this with multiple tools, parameter handling, and YAML-driven organization configurations, showcasing tool chaining to discover org IDs and pass them to network listing operations, and scaling across multiple organizations. The enhanced declarative Meraki and Catalyst servers add declarative tooling and API exploration capabilities, enabling Cosine-search style discovery of APIs from API specs, with restricted GET-only access for safety. You can run these servers as subprocesses via the MCP Client and use their tools to discover, call, and document Meraki and Catalyst Center APIs across one or more organizations.

Prerequisites:

• Python 3.8+ installed on your system
• pip available in your PATH
• Access credentials for Meraki and Catalyst Center APIs

Installation steps:

1. Clone the repository containing the MCP servers and navigate to the project directory.
2. Install Python dependencies:
   • python -m pip install -r requirements.txt
3. Prepare credentials and environment files:
   • Create environment.env with your API keys and endpoints (MERAKI_PROD_API_KEY, MERAKI_LAB_API_KEY, CC_URL, CC_USER, CC_PASS).
   • If using YAML configurations, ensure meraki_organizations.yaml and catalyst_center_clusters.yaml are properly configured as shown in the README.
4. Run the servers (examples):
   • python basic_meraki_mcp_server.py
   • python foundation_meraki_mcp_server.py
   • python multiorg_meraki_mcp_server.py
   • python enhanced_declarative_meraki.py
   • python enhanced_declarative_catalyst.py
5. Verify servers are running locally; the MCP Client will start and manage subprocesses for these servers.

Tips and common issues:

• Ensure your API keys have the required permissions for Meraki and Catalyst Center; rotate keys as needed and update environment.env accordingly.
• If using multiple environments (Prod/Lab), keep API keys separate and use meraki_organizations.yaml to map per-org credentials.
• When enabling YAML-driven org configurations, verify the syntax and keys in meraki_organizations.yaml and catalyst_center_clusters.yaml to avoid parsing errors.
• For safety, the enhanced declarative servers restrict API exploration to GET endpoints; ensure your API specs reflect accessible resources.
• If you encounter module import errors, re-create a virtual environment and re-install dependencies from requirements.txt.
• Use the provided Cosine-like API exploration features to quickly locate APIs, generate API docs, and telemetry for auditing purposes.