An Ansible collection for managing Meraki Dashboard resources using the resource module pattern. Configuration is expressed as declarative desired state (merged, replaced, overridden, gathered, deleted) and reconciled against the live API.
The collection includes 48 resource modules, a dynamically generated MCP server for AI agent integration, and a CLI tool — all driven by a single set of User Model dataclasses.
- name: Ensure VLAN 100 exists
cisco.meraki_rm.meraki_appliance_vlans:
state: merged
network_id: L_123456
config:
- vlan_id: 100
name: Engineering
subnet: 10.100.0.0/24
appliance_ip: 10.100.0.1ansible-galaxy collection install cisco.meraki_rmFor the MCP server and CLI (standalone Python package):
pip install './plugins/plugin_utils/[mcp,cli]'| Doc | Description |
|---|---|
| Overview | Project goals, scope, and high-level architecture |
| Resource Module Pattern | The state-driven CRUD pattern all modules follow |
| SDK Architecture | Internal package layout, install modes, and extension points |
| Data Model Transformation | How user-facing snake_case maps to API camelCase |
| Design Principles | Architectural guardrails, validation strategy, and quality gates |
| Doc | Description |
|---|---|
| Foundation Components | PlatformService, BaseResourceActionPlugin, User Models |
| Adding Resources | Step-by-step guide for adding a new resource module |
| Code Generators | Schema extraction, model generation, doc generation tooling |
| Meraki Implementation Guide | Meraki-specific patterns, endpoint grouping, and identity categories |
| Doc | Description |
|---|---|
| MCP Server Reference | AI agent integration via Model Context Protocol |
| CLI Reference | meraki-cli command-line tool for direct API interaction |
| Doc | Description |
|---|---|
| Testing Strategy | Unit tests, Molecule integration tests, and mock server |
| Doc | Description |
|---|---|
| Agent Collaboration Guide | Working with AI agents on the codebase |
| Case Study: NovaCom | Fictional walkthrough illustrating the framework in action |
| Doc | Description |
|---|---|
| Feedback Questions | Structured questions for Meraki stakeholder review |
| API Limitations | How API design drives module states and identity categories |
| Coverage Report | Spec-vs-module coverage analysis (auto-generated) |
plugins/
action/ # Action plugins (one per resource)
modules/ # Module definitions (DOCUMENTATION + argspec)
plugin_utils/ # Shared SDK: User Models, PlatformService, MCP, CLI
tools/ # Code generators, mock server, doc renderers
tests/ # Unit and integration tests
extensions/ # Molecule test scenarios
docs/ # Architecture and reference documentation
examples/ # Per-module Ansible playbook examples
See LICENSE.