@usex/mikrotik-mcp 5.22.0 → 6.1.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.
- package/README.md +17 -6
- package/dist/cli.js +702 -241
- package/dist/index.js +1 -1
- package/dist/shared/{library-nxgjnp8e.js → library-039808cq.js} +1 -1
- package/dist/shared/{library-swqk16r2.js → library-53nrt1xj.js} +1 -1
- package/dist/shared/{library-0ej78km8.js → library-7nnp4ntt.js} +1 -1
- package/dist/shared/{library-8ve5x0t1.js → library-ph2n6fjm.js} +1 -1
- package/dist/shared/{library-hbxz5fg7.js → library-qt6rx1ht.js} +360 -105
- package/dist/ui/observability.html +75 -75
- package/package.json +7 -5
- package/schemas/README.md +1 -1
- package/schemas/devtools-manifest.json +40 -2
- package/schemas/tool-catalog.json +125 -32
- package/schemas/tools/get_wireless_interface.json +2 -1
- package/schemas/tools/get_wireless_interface_status.json +13 -0
- package/schemas/tools/get_wireless_security_profile.json +2 -1
- package/schemas/tools/lookup_ip_intelligence.json +13 -0
- package/schemas/tools/resolve_dns.json +4 -2
- package/schemas/tools/scan_wifi_channels.json +24 -0
- package/schemas/tools/scan_wireless_networks.json +10 -4
- package/schemas/tools/test_dns_query.json +8 -3
- /package/dist/shared/{cli-a5tef6t8.js → cli-8h5ye8pv.js} +0 -0
- /package/dist/shared/{cli-0v69rn38.js → cli-92qtg8n3.js} +0 -0
- /package/dist/shared/{cli-8tmbrnm5.js → cli-ncmy3wt1.js} +0 -0
- /package/dist/shared/{cli-v5brt13c.js → cli-y746q0cw.js} +0 -0
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
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 —
|
|
3
|
+
<p><strong>Drive one or more MikroTik routers in plain language — 950 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>
|
|
@@ -46,8 +46,9 @@ Then just ask:
|
|
|
46
46
|
|
|
47
47
|
## Highlights
|
|
48
48
|
|
|
49
|
+
- **IP Intelligence:** `lookup_ip_intelligence` and Diagnostics → IP Intelligence compare full ipquery/ipkit responses: ASN/organization, location, risk and every additional field, with searchable details and JSON export. Public IPs are sent only on submission; private IPs stay local. [Guide](docs/ip-intelligence.md).
|
|
49
50
|
- **Service probes:** add, edit, search and remove approved HTTPS/TLS/TCP/DNS targets directly in Config or Service Routing, with explicit IP/CIDR boundaries and safe-apply confirmation. [Setup guide](docs/service-contracts.md#dashboard-setup-no-json-required).
|
|
50
|
-
- **OpenVPN connections:**
|
|
51
|
+
- **OpenVPN connections:** active users, source/tunnel IPs, cached country flags and ASN organizations, searchable source networks and live connection time, with confirmed single-session disconnect and read-only access controls. [Guide](docs/openvpn-connections.md).
|
|
51
52
|
- **Service Routing:** live IPv4/IPv6 routes, fuzzy address-list search, exact/wildcard domain-to-exit policies with optional health probes, per-policy live matched-traffic counters and charts, VRF HTTPS exit checks and
|
|
52
53
|
explicitly authorized failover, with preview, backup and Safe Mode. [Guide](docs/service-routing.md)
|
|
53
54
|
- **Flight Recorder:** opt-in, durable pre/post-incident telemetry and log metadata,
|
|
@@ -235,9 +236,15 @@ mikrotik-mcp devices # site-a (default) · site-b
|
|
|
235
236
|
#### Docker: one writable `devices.json` for all MCP settings
|
|
236
237
|
|
|
237
238
|
Use the published **[alimaster/mikrotik-mcp](https://hub.docker.com/r/alimaster/mikrotik-mcp)**
|
|
238
|
-
image (`
|
|
239
|
+
image (`6.0.0`, or the moving `latest` tag). Docker selects `linux/amd64` or
|
|
239
240
|
`linux/arm64` automatically; no local build is needed. Compose defaults to
|
|
240
|
-
`
|
|
241
|
+
`6.0.0`; set `MIKROTIK_IMAGE_TAG` explicitly to select a different release.
|
|
242
|
+
|
|
243
|
+
**Not ARM-only:** the same image runs on x86-64 and ARM64 Linux hosts (including
|
|
244
|
+
Ubuntu), and on Windows/macOS through Docker Desktop's **Linux containers**.
|
|
245
|
+
Windows users should enable the WSL2 backend; do not select Windows containers.
|
|
246
|
+
See the [host compatibility and PowerShell quick start](docs/docker.md#host-compatibility)
|
|
247
|
+
for platform-specific setup. Neither Compose nor the runtime is pinned to ARM.
|
|
241
248
|
|
|
242
249
|
The Bun container reads **`/home/bun/.mikrotik-mcp/devices.json`** automatically.
|
|
243
250
|
Despite its name, this is the **complete MCP configuration**, not just the router
|
|
@@ -268,13 +275,13 @@ Create a real JSON file on the host (no comments or trailing commas). For exampl
|
|
|
268
275
|
```
|
|
269
276
|
|
|
270
277
|
```bash
|
|
271
|
-
docker pull alimaster/mikrotik-mcp:
|
|
278
|
+
docker pull alimaster/mikrotik-mcp:6.0.0
|
|
272
279
|
docker run -d --name mikrotik-mcp --restart unless-stopped \
|
|
273
280
|
-p 127.0.0.1:8000:8000 -p 127.0.0.1:9090:9090 \
|
|
274
281
|
--mount type=volume,src=mikrotik-state,dst=/home/bun/.mikrotik-mcp \
|
|
275
282
|
--mount type=bind,src=/absolute/path/devices.json,dst=/home/bun/.mikrotik-mcp/devices.json \
|
|
276
283
|
--mount type=bind,src=/absolute/path/mikrotik_ed25519,dst=/run/secrets/mikrotik_key,readonly \
|
|
277
|
-
alimaster/mikrotik-mcp:
|
|
284
|
+
alimaster/mikrotik-mcp:6.0.0
|
|
278
285
|
```
|
|
279
286
|
|
|
280
287
|
Dashboard: **http://localhost:9090** · MCP: **http://localhost:8000/mcp**.
|
|
@@ -445,6 +452,10 @@ and last-seen.
|
|
|
445
452
|
|
|
446
453
|
**RADIUS & User Manager.** Servers, sessions, profiles, limitations and vouchers.
|
|
447
454
|
|
|
455
|
+
The **Users** table also shows each user's last recorded connection date and time
|
|
456
|
+
(router-local time), using a separate background cache so traffic counters stay fast.
|
|
457
|
+
See [last connection reporting](docs/user-manager-last-connections.md).
|
|
458
|
+
|
|
448
459
|
In **Users → Edit → Service profile**, keep the current profile or choose another
|
|
449
460
|
profile on the selected router. Saving reuses an eligible assignment (or creates
|
|
450
461
|
one), activates it and verifies the result. Previous assignments and accounting
|