@usex/mikrotik-mcp 5.19.0 → 5.21.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (74) hide show
  1. package/README.md +180 -8
  2. package/dist/cli.js +3452 -729
  3. package/dist/index.js +148 -27
  4. package/dist/shared/{library-ppnv0f07.js → library-588vnctn.js} +1 -1
  5. package/dist/shared/{library-7wcv2ckk.js → library-6tvh3gq1.js} +2837 -545
  6. package/dist/shared/{library-tqrvrykj.js → library-g8far2nz.js} +1 -1
  7. package/dist/shared/{library-f3be6g03.js → library-k6m2bxjr.js} +1 -1
  8. package/dist/shared/{library-z7qsdq88.js → library-wj2xfx8h.js} +1 -1
  9. package/dist/ui/aaa.html +8 -8
  10. package/dist/ui/connected-devices.html +8 -8
  11. package/dist/ui/dashboard.html +16 -16
  12. package/dist/ui/fabric.html +11 -11
  13. package/dist/ui/firewall-audit.html +8 -8
  14. package/dist/ui/firewall.html +9 -9
  15. package/dist/ui/interfaces.html +8 -8
  16. package/dist/ui/investigations.html +11 -11
  17. package/dist/ui/observability.html +66 -62
  18. package/dist/ui/operations.html +11 -11
  19. package/dist/ui/records.html +12 -12
  20. package/dist/ui/reports.html +11 -11
  21. package/dist/ui/round-trip.html +11 -11
  22. package/dist/ui/service-health.html +11 -11
  23. package/package.json +24 -23
  24. package/prompts/audit-routeros-containers.md +27 -0
  25. package/prompts/audit-vlan-segmentation.md +31 -0
  26. package/prompts/setup-guest-wifi.md +23 -24
  27. package/prompts/setup-routeros-container.md +36 -0
  28. package/prompts/setup-v2ray-container-proxy.md +68 -194
  29. package/prompts/setup-vlan-network.md +27 -33
  30. package/schemas/README.md +1 -1
  31. package/schemas/devtools-manifest.json +327 -16
  32. package/schemas/tool-catalog.json +898 -109
  33. package/schemas/tools/add_container.json +42 -30
  34. package/schemas/tools/add_container_env.json +3 -4
  35. package/schemas/tools/add_container_mount.json +10 -4
  36. package/schemas/tools/apply_service_routing.json +23 -0
  37. package/schemas/tools/arm_service_routing.json +23 -0
  38. package/schemas/tools/configure_flight_recorder.json +30 -0
  39. package/schemas/tools/create_service_routing.json +91 -0
  40. package/schemas/tools/design_network_segment.json +22 -6
  41. package/schemas/tools/destroy_recovery_lab.json +18 -0
  42. package/schemas/tools/disconnect_ovpn_session.json +20 -0
  43. package/schemas/tools/export_network_incident.json +14 -0
  44. package/schemas/tools/freeze_network_incident.json +14 -0
  45. package/schemas/tools/get_container.json +11 -4
  46. package/schemas/tools/get_flight_recorder.json +7 -0
  47. package/schemas/tools/get_recovery_lab.json +7 -0
  48. package/schemas/tools/get_routeros_container_guide.json +22 -0
  49. package/schemas/tools/get_vlan_segmentation_guide.json +14 -0
  50. package/schemas/tools/list_container_envs.json +1 -1
  51. package/schemas/tools/list_container_mounts.json +7 -2
  52. package/schemas/tools/list_containers.json +2 -4
  53. package/schemas/tools/list_ovpn_sessions.json +7 -0
  54. package/schemas/tools/list_service_routing.json +7 -0
  55. package/schemas/tools/poll_recovery_lab.json +14 -0
  56. package/schemas/tools/prepare_recovery_lab.json +23 -0
  57. package/schemas/tools/preview_service_routing.json +23 -0
  58. package/schemas/tools/probe_service_routing.json +14 -0
  59. package/schemas/tools/recovery_lab_inventory.json +7 -0
  60. package/schemas/tools/remove_container.json +11 -4
  61. package/schemas/tools/remove_container_env.json +7 -3
  62. package/schemas/tools/remove_container_mount.json +18 -2
  63. package/schemas/tools/service_routing_address_page.json +19 -0
  64. package/schemas/tools/service_routing_inventory.json +7 -0
  65. package/schemas/tools/service_routing_traffic.json +14 -0
  66. package/schemas/tools/set_container_config.json +4 -6
  67. package/schemas/tools/start_container.json +11 -4
  68. package/schemas/tools/start_recovery_lab.json +18 -0
  69. package/schemas/tools/stop_container.json +11 -4
  70. package/schemas/tools/update_container.json +46 -6
  71. /package/dist/shared/{cli-j07tbrke.js → cli-h065ap70.js} +0 -0
  72. /package/dist/shared/{cli-s0rxncz4.js → cli-se3tgt7t.js} +0 -0
  73. /package/dist/shared/{cli-y00nwzxx.js → cli-t311px0m.js} +0 -0
  74. /package/dist/shared/{cli-gtq5bw8q.js → cli-wf9a7qjm.js} +0 -0
@@ -1,47 +1,41 @@
1
1
  ---
2
2
  name: setup-vlan-network
3
- title: Design and deploy VLAN segments
4
- description: Create isolated VLAN segments with gateway addressing, DHCP, and inter-VLAN firewall policy — previewed before apply.
3
+ title: Design a safe dual-stack VLAN migration
4
+ description: Audit the existing topology and plan VLAN ports, SSIDs, management access, IPv4/IPv6 policy and staged verification before any approved change.
5
5
  arguments:
6
6
  - name: vlans
7
7
  description: Describe the VLANs you need — e.g. "management=10, staff=20, IoT=30, guest=40" (name=VLAN-ID).
8
8
  required: true
9
9
  - name: trunk_interface
10
- description: The interface to use as a VLAN trunk (e.g. "ether1", "bridge"). If omitted, the main bridge is used.
10
+ description: Optional proposed physical trunk. If omitted, discover and confirm the port map; never assume a bridge or WAN port is the trunk.
11
11
  required: false
12
12
  ---
13
13
 
14
- Design and deploy a VLAN-segmented network on this MikroTik device. Each VLAN
15
- gets its own subnet, gateway IP, DHCP server, and firewall isolation. All changes
16
- are previewed before applying.
14
+ Plan a VLAN-segmented network on the explicitly selected MikroTik device.
15
+ Start read-only. A design request is NOT permission to apply it.
17
16
 
18
17
  VLANs requested: {{vlans}}
19
18
  Trunk interface: {{trunk_interface}}
20
19
 
21
- Follow these steps — confirm the plan before applying any changes:
22
-
23
- 1. **Understand the current layout.** Call `list_interfaces`, `list_bridges`,
24
- `list_ip_addresses`, and `list_dhcp_servers` to understand what exists.
25
-
26
- 2. **Design each VLAN segment.** For each VLAN in {{vlans}}, call
27
- `design_network_segment` in **preview mode** with:
28
- - VLAN ID and name.
29
- - A subnet (auto-assigned or specified — e.g. 10.10.{vlan_id}.0/24).
30
- - Gateway address (.1 in the subnet).
31
- - DHCP pool range.
32
- - Isolation policy (whether this VLAN can reach others).
33
-
34
- 3. **Review the plan.** Present a summary table:
35
- - VLAN ID, name, subnet, gateway, DHCP range.
36
- - Firewall rules that will be created for inter-VLAN isolation.
37
- - Bridge/trunk configuration changes.
38
-
39
- 4. **Apply.** With user approval, run `design_network_segment` again with apply
40
- mode for each VLAN.
41
-
42
- 5. **Verify.** Call `list_vlan_interfaces` to confirm VLANs are created,
43
- `list_ip_addresses` for gateway IPs, `list_dhcp_servers` for DHCP, and
44
- `list_filter_rules` for the isolation firewall rules.
45
-
46
- Report the complete VLAN map and any follow-ups (e.g. switch port VLAN
47
- assignments, wireless SSID-to-VLAN mappings).
20
+ 1. Discover the current bridge, ports, CPU membership, Wi-Fi package/SSID mapping,
21
+ addresses, DHCP, IPv6, both firewall families and routing dependencies using
22
+ `find_tools`. Resolve management/recovery access and ambiguous port roles first.
23
+ 2. Present a per-device VLAN map: role, ID, subnet, gateway, DHCP pool, IPv6 /64,
24
+ SSID, access ports/PVIDs, allowed trunk VLANs and bridge/CPU membership. Do not
25
+ allocate conflicting subnets or assume every role needs its own VLAN.
26
+ 3. Show an IPv4/IPv6 INPUT and FORWARD service matrix and exact rule placement.
27
+ Include remote-site return routes and VPN allowed-addresses only if affected.
28
+ Flag policy routing, NAT, FastTrack, queues and scripts tied to old interfaces.
29
+ 4. Present ordered steps, prerequisites, backup/rollback and canary tests. Enable
30
+ filtering LAST; do not disable existing filtering during migration. Do not
31
+ silently renumber the working LAN or expose management to every trusted client.
32
+ 5. `design_network_segment` may preview partial IPv4 scaffolding only. It is NOT
33
+ a full migration or isolation engine. Discover its schema and account for all
34
+ omitted L2/SSID/INPUT/IPv6/routing work; do not apply it once per VLAN blindly.
35
+ 6. Stop for approval of the exact changes. For approved dependent multi-router
36
+ writes, use the coordinated transaction workflow if available and suitable.
37
+ Never run transaction verification during a read-only audit: it performs writes.
38
+ 7. After approved changes, read back and test real wired and wireless clients for
39
+ intended allows AND denies over both families. List unverified tests explicitly;
40
+ configuration creation alone is not proof of isolation. Clean up only after
41
+ validation and dependency review, with separate approval for removals.
package/schemas/README.md CHANGED
@@ -7,7 +7,7 @@ edit by hand — regenerate instead.
7
7
  | File | Contents |
8
8
  | -------------------- | ------------------------------------------------------------------------------------------ |
9
9
  | `config.schema.json` | The runtime configuration object (env vars / CLI flags). |
10
- | `tool-catalog.json` | Every one of the 937 tools: `name`, `risk`, `title`, `description`, and input JSON Schema. |
10
+ | `tool-catalog.json` | Every one of the 960 tools: `name`, `risk`, `title`, `description`, and input JSON Schema. |
11
11
  | `tools/<name>.json` | The input JSON Schema for a single tool. |
12
12
 
13
13
  `risk` is derived from the MCP tool annotations: