@usex/mikrotik-mcp 5.16.0 → 5.17.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 (31) hide show
  1. package/README.md +58 -4
  2. package/dist/cli.js +5966 -4114
  3. package/dist/index.js +12 -10
  4. package/dist/shared/cli-51yqa57b.js +25 -0
  5. package/dist/shared/cli-5rs21zfv.js +13 -0
  6. package/dist/shared/cli-s1kg75zm.js +7 -0
  7. package/dist/shared/{library-0ysgbdj6.js → library-85ayxzg9.js} +7657 -6682
  8. package/dist/shared/library-b7vtz46e.js +7 -0
  9. package/dist/shared/library-rw1d7smw.js +13 -0
  10. package/dist/shared/library-xw54vgxq.js +17 -0
  11. package/dist/shared/{library-pdyv4a32.js → library-y97z4cef.js} +1 -1
  12. package/dist/ui/client-check.html +80 -0
  13. package/dist/ui/observability.html +136 -75
  14. package/package.json +19 -7
  15. package/schemas/README.md +1 -1
  16. package/schemas/devtools-manifest.json +11933 -0
  17. package/schemas/tool-catalog.json +409 -2
  18. package/schemas/tools/apply_router_migration.json +27 -0
  19. package/schemas/tools/close_client_check.json +14 -0
  20. package/schemas/tools/compare_client_checks.json +24 -0
  21. package/schemas/tools/create_client_check.json +25 -0
  22. package/schemas/tools/create_support_bundle.json +41 -0
  23. package/schemas/tools/delete_support_bundle.json +18 -0
  24. package/schemas/tools/export_support_bundle.json +19 -0
  25. package/schemas/tools/inspect_router_migration.json +7 -0
  26. package/schemas/tools/list_client_checks.json +7 -0
  27. package/schemas/tools/list_router_migrations.json +7 -0
  28. package/schemas/tools/list_support_bundles.json +7 -0
  29. package/schemas/tools/preview_router_migration.json +62 -0
  30. package/schemas/tools/undo_router_migration.json +18 -0
  31. /package/dist/shared/{cli-gee7615j.js → cli-s5nnez6j.js} +0 -0
package/README.md CHANGED
@@ -1,20 +1,20 @@
1
1
  <div align="center">
2
2
  <img src="assets/logo.svg" alt="@usex/mikrotik-mcp" width="440" />
3
- <p><strong>Drive one or more MikroTik routers in plain language — 901 risk-annotated tools your AI can call, over SSH.</strong><br/>
3
+ <p><strong>Drive one or more MikroTik routers in plain language — 924 risk-annotated tools your AI can call, over SSH.</strong><br/>
4
4
  Firewall · routing · DHCP/DNS · wireless · QoS · a complete VPN suite · transactional Safe Mode · live attack detection · and an observability dashboard that watches every call.</p>
5
5
 
6
6
  <p>
7
7
  <a href="LICENSE"><img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-7C3AED.svg"></a>
8
8
  <img alt="Runtime: Bun" src="https://img.shields.io/badge/runtime-Bun%20%E2%89%A5%201.3-06B6D4.svg">
9
9
  <img alt="TypeScript" src="https://img.shields.io/badge/TypeScript-strict-6366F1.svg">
10
- <img alt="MCP" src="https://img.shields.io/badge/MCP-901%20tools-1F2937.svg">
10
+ <img alt="MCP" src="https://img.shields.io/badge/MCP-924%20tools-1F2937.svg">
11
11
  <a href="docs/"><img alt="Docs" src="https://img.shields.io/badge/docs-reference-7C3AED.svg"></a>
12
12
  </p>
13
13
  </div>
14
14
 
15
15
  ---
16
16
 
17
- `@usex/mikrotik-mcp` turns **MikroTik RouterOS** into **901 [Model Context Protocol](https://modelcontextprotocol.io)
17
+ `@usex/mikrotik-mcp` turns **MikroTik RouterOS** into **924 [Model Context Protocol](https://modelcontextprotocol.io)
18
18
  tools** any MCP client (Claude Desktop, Claude Code, Cursor, …) can call to read and
19
19
  configure your router by talking to it. It reaches the device over **plain SSH** — no
20
20
  agent, no package to install on RouterOS — runs on **[Bun](https://bun.sh)**, and
@@ -46,6 +46,21 @@ Then just ask:
46
46
 
47
47
  ## Highlights
48
48
 
49
+ - **Client Check** — invite the affected phone/laptop with an expiring QR/link,
50
+ measure browser HTTP latency, loaded latency and bounded transfers, and compare
51
+ Wi-Fi/VPN runs in the dashboard. Optional investigation links keep evidence together.
52
+ Tests measure the path **to the MCP host**, not arbitrary internet speed, DNS leakage
53
+ or PMTU. [Guide and trust boundary](docs/network-workspaces.md#client-check)
54
+ - **Router Migration** — inspect both routers, map Ethernet ports, preview supported
55
+ configuration and review omitted sections. Fresh-state checks, local snapshots of
56
+ both routers, Safe Mode rehearsal and verified **inactive staging** protect the
57
+ target. Physical cutover, credentials and activation remain operator-controlled.
58
+ [Supported scope](docs/network-workspaces.md#router-migration)
59
+ - **Support Bundles** — prepare a time-bounded report from saved investigations,
60
+ event metadata, snapshot inventories and client measurements. Raw tool bodies,
61
+ secrets and personal labels stay out; network identifiers become consistent aliases.
62
+ Review before downloading self-contained HTML or JSON. Nothing is uploaded.
63
+ [Privacy and export](docs/network-workspaces.md#support-bundles)
49
64
  - **MCP App workspaces** — 13 host-themed views, with dedicated investigation,
50
65
  round-trip, service-health, L2 fabric, operations and report workspaces alongside
51
66
  the existing device, interface, firewall and record views. Responsive grids,
@@ -71,7 +86,7 @@ Then just ask:
71
86
  Uses existing NetFlow/IPFIX exports; never enables capture or changes router settings.
72
87
  Missing telemetry remains unknown, not a fabricated blocking hop.
73
88
  [Flow-path guide](docs/client-flow-paths.md)
74
- - 🧰 **901 tools, one per RouterOS scope** — L2 (bridge, VLAN, wireless, PoE),
89
+ - 🧰 **924 tools, one per RouterOS scope** — L2 (bridge, VLAN, wireless, PoE),
75
90
  L3 (addressing, routing, DHCP, DNS), security (firewall, NAT, address-lists,
76
91
  certificates), QoS, and system ops (users, logs, backups, scheduler).
77
92
  - 🛡️ **Attack detection** — reads every device's log, correlates brute force,
@@ -389,6 +404,36 @@ For frontend development, `bun run dev:dashboard` connects
389
404
  the UI on port 9191 to the existing dashboard backend on port 9091.
390
405
  See the [dashboard design system](docs/dashboard-design.md).
391
406
 
407
+ ### DevFrame developer tools
408
+
409
+ Run the dashboard backend and the DevTools frontend in **two terminals** from
410
+ the repository root:
411
+
412
+ ```sh
413
+ # Terminal 1 — MCP server and dashboard API
414
+ bun run start:dev --dashboard --dashboard-port 9091 --config /path/to/devices.json
415
+
416
+ # Terminal 2 — dashboard frontend with DevFrame enabled
417
+ bun run dev:tools
418
+ ```
419
+
420
+ Open **http://127.0.0.1:9191/** and authorize the DevFrame dock with the one-time
421
+ code printed in the development terminal when prompted. If the port is occupied,
422
+ run `bun run dev:tools --port 9194` and open **http://127.0.0.1:9194/** instead.
423
+ The backend stays on port **9091**; `start:dev` alone does not enable DevFrame.
424
+
425
+ - **Data Inspector:** explore tool schemas, modules, prompts, App View coverage,
426
+ device requirements, navigation and build diagnostics.
427
+ - **Devframe Inspector:** enable **Settings → Advanced → Show Devframe Inspector**,
428
+ then filter **Functions** by `mikrotik:` for read-only MCP inspection queries.
429
+ - **A11y Inspector:** audit the current dashboard page for accessibility issues.
430
+
431
+ After changing tool declarations, run `bun run gen:schemas` to refresh the public
432
+ inspection data. Run `bun run build:ui` to populate build-artifact diagnostics.
433
+ DevFrame is development-only: it is not embedded in production builds, does not
434
+ load device credentials, and does not expose another router-execution endpoint.
435
+ See the [DevTools guide](docs/devtools.md) for search examples and security boundaries.
436
+
392
437
  **Access Scope settings** can be edited directly in the dashboard: configure risk
393
438
  ceilings, router allow/block lists and tool-name patterns, preview permission
394
439
  decisions without executing tools, then review and apply with a 60-second
@@ -466,6 +511,15 @@ MCP **prompts** are one-click guided workflows — authored as Markdown in
466
511
 
467
512
  See **[docs/prompts.md](docs/prompts.md)**.
468
513
 
514
+ Browse the live library under **Workspace → Prompts** in the dashboard, or run
515
+ **Prompt Library** in Raycast (also available in the Fleet Menu Bar). Search and
516
+ filter workflows, fill their required inputs, add your own request and target
517
+ router, then preview and copy the completed brief into an MCP-connected assistant.
518
+ Nothing runs on a router while composing. The dashboard links open ChatGPT/Claude
519
+ without including your request in the URL; paste and send it yourself. Raycast also
520
+ offers **Ask Raycast AI for a Plan** when AI access is available: this sends the
521
+ request to Raycast AI for advice, not MCP tool execution.
522
+
469
523
  ## Transports
470
524
 
471
525
  | Transport | When | Run |