@usex/mikrotik-mcp 2.5.0 → 3.1.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@usex/mikrotik-mcp",
-  "version": "2.5.0",
-  "description": "Bun-native MCP server for MikroTik RouterOS — 200+ tools over SSH for firewall, NAT, routing, DHCP, DNS, WireGuard, wireless, QoS and more.",
+  "version": "3.1.0",
+  "description": "MCP server for MikroTik RouterOS — 660+ tools over SSH for firewall, NAT, routing, DHCP, DNS, WireGuard, wireless, QoS and more.",
   "keywords": [
     "ai",
     "bun",
@@ -10,7 +10,7 @@
     "mikrotik",
     "mikrotik mcp"
   ],
-  "homepage": "https://github.com/ali-master/mikrotik-mcp#readme",
+  "homepage": "https://mikrotik-mcp.usestrict.dev",
   "bugs": {
     "url": "https://github.com/ali-master/mikrotik-mcp/issues"
   },
@@ -89,6 +89,7 @@
     "@types/ssh2": "^1.15.5",
     "@types/update-notifier": "^6.0.8",
     "bunup": "^0.16.32",
+    "gsap": "^3.15.0",
     "prettier": "^3.8.4",
     "react": "^19.2.7",
     "react-dom": "^19.2.7",
@@ -119,5 +120,6 @@
       "breaking change": "Breaking changes"
     }
   },
-  "logo": "https://raw.githubusercontent.com/ali-master/mikrotik-mcp/master/assets/logo.svg"
+  "logo": "https://raw.githubusercontent.com/ali-master/mikrotik-mcp/master/assets/logo.svg",
+  "logoIcon": "https://raw.githubusercontent.com/ali-master/mikrotik-mcp/master/assets/logo-icon.svg"
 }

package/prompts/backup-and-document.md

@@ -4,6 +4,7 @@ title: Back up and document the configuration
 description: Create a safe restore point and produce a human-readable inventory of the router's configuration.
 arguments: []
 ---
+
 Create a restore point for this MikroTik device and then write up a clear,
 human-readable summary of how it's configured. This is read-mostly: the only
 change is creating a backup/export.

package/prompts/choose-vpn-solution.md

@@ -10,6 +10,7 @@ arguments:
     description: What connects — e.g. "iOS/Android/Windows built-in clients", "other MikroTik routers", "a Cisco/Fortinet device", "our laptops only". Optional.
     required: false
 ---
+
 Act as a MikroTik VPN architect. Recommend the single best tunneling technology
 for the requirement below, justify it against the alternatives, then sketch the
 build using this server's tools. Be decisive.
@@ -23,7 +24,7 @@ Decision guidance — weigh these MikroTik options:
   laptops/phones with the WireGuard app. No built-in OS client on older systems.
   Tools: `create_wireguard_interface`, `add_wireguard_peer`, `generate_wireguard_client_config`.
 - **IPsec (IKEv2)** — the interoperability choice for site-to-site with
-  *other vendors* (Cisco/Fortinet/pfSense) and for native iOS/Windows IKEv2
+  _other vendors_ (Cisco/Fortinet/pfSense) and for native iOS/Windows IKEv2
   road-warrior. Most config surface. Tools: `create_ipsec_*` (profile/peer/
   identity/proposal/policy), `get_ipsec_active_peers`.
 - **L2TP/IPsec** — best when clients must use the **built-in** VPN client on
@@ -34,7 +35,7 @@ Decision guidance — weigh these MikroTik options:
 - **OpenVPN** — cross-platform with the OpenVPN client; RouterOS 7 adds UDP.
   Tools: `set_ovpn_server`, `create_ovpn_client`.
 - **PPTP** — legacy/weak; only if a legacy device demands it. Recommend against.
-- **GRE / IPIP / EoIP / VXLAN** — *unencrypted* transport tunnels for routing or
+- **GRE / IPIP / EoIP / VXLAN** — _unencrypted_ transport tunnels for routing or
   L2 bridging between sites (often run **over** an IPsec policy for encryption).
   EoIP/VXLAN bridge layer-2; GRE/IPIP carry layer-3. Tools: `create_gre_tunnel`,
   `create_eoip_tunnel`, `create_vxlan_tunnel`.

package/prompts/diagnose-connectivity.md

@@ -10,6 +10,7 @@ arguments:
     description: The interface/segment the affected clients are on (e.g. bridge, vlan50). Optional.
     required: false
 ---
+
 Troubleshoot a connectivity issue on a MikroTik RouterOS device, reasoning from
 the bottom of the stack up. Use read-only tools only — do not change config until
 you've localized the fault and the user approves a fix.

package/prompts/harden-router.md

@@ -7,6 +7,7 @@ arguments:
     description: The WAN-facing interface name (e.g. ether1, pppoe-out1). If unknown, discover it first.
     required: false
 ---
+
 You are securing a MikroTik RouterOS device exposed through this MCP server. Work
 **safely and incrementally**: inspect first, propose a plan, and prefer Safe Mode
 for risky firewall changes so a mistake auto-reverts instead of locking us out.

package/prompts/setup-guest-wifi.md

@@ -13,6 +13,7 @@ arguments:
     description: The interface that reaches the internet (for the masquerade rule).
     required: true
 ---
+
 Build an **isolated guest network** on this MikroTik device. Guests must reach the
 internet but must NOT reach the LAN or the router's management. Plan the whole
 change first, show it to the user, then apply it under Safe Mode.
@@ -35,8 +36,8 @@ Proposed build (adapt to what you discover with `list_interfaces`,
    `create_filter_rule`:
    - allow {{subnet}} → WAN (established/related + new),
    - **drop {{subnet}} → LAN subnets (RFC1918)**,
-   and in the `input` chain drop {{subnet}} → router except DHCP/DNS. Consider an
-   `add_address_list_entry` list named `guest` to keep the rules tidy.
+     and in the `input` chain drop {{subnet}} → router except DHCP/DNS. Consider an
+     `add_address_list_entry` list named `guest` to keep the rules tidy.
 6. **Verify** — re-list the rules and confirm ordering; `enable_safe_mode` before
    applying, test, then `commit_safe_mode`.
 

package/prompts/setup-ipsec-site-to-site.md

@@ -13,6 +13,7 @@ arguments:
     description: The public IP / hostname of the remote peer.
     required: true
 ---
+
 Build a secure IPsec **IKEv2** site-to-site tunnel. IKEv2 is the interoperability
 choice — it works against other MikroTik routers and third-party firewalls
 (Cisco, Fortinet, pfSense). Plan first, present the parameters for both ends to
@@ -39,7 +40,7 @@ identical on both ends):
    `dst_address={{remote_subnet}}`, `tunnel=true`, `action=encrypt`, the peer, and
    the proposal.
 6. **Firewall / NAT** — ensure UDP 500 + 4500 and IP protocol 50 (ESP) are
-   accepted from {{peer_address}} on the input chain, and add a NAT *bypass*
+   accepted from {{peer_address}} on the input chain, and add a NAT _bypass_
    (accept/no-nat) rule so {{local_subnet}}→{{remote_subnet}} traffic is NOT
    masqueraded. Apply firewall edits under `enable_safe_mode`.
 7. **Verify** — `get_ipsec_active_peers` and `get_ipsec_installed_sa` to confirm

package/prompts/setup-l2tp-ipsec-roadwarrior.md

@@ -10,6 +10,7 @@ arguments:
     description: The router's address on the VPN/LAN side that clients use as gateway/DNS, e.g. 192.168.89.1.
     required: true
 ---
+
 Configure **L2TP/IPsec** remote access — the right choice when users must connect
 with the **built-in** VPN client on Windows, macOS, iOS, and Android (no app to
 install). Plan first, then apply (firewall under Safe Mode).

package/prompts/setup-tunnel-between-sites.md

@@ -13,6 +13,7 @@ arguments:
     description: Tunnel type to use — wireguard, ipsec, gre, eoip, or "recommend" to let you choose.
     required: false
 ---
+
 You are configuring a **site-to-site tunnel between two MikroTik routers** that
 this server can both reach. You will drive BOTH devices in one flow by passing
 the `device` argument on each tool call.

package/prompts/setup-wireguard-vpn.md

@@ -13,6 +13,7 @@ arguments:
     description: UDP port for WireGuard (default 13231).
     required: false
 ---
+
 Provision a WireGuard VPN on this MikroTik device and produce a working client
 config. Confirm the plan with the user before applying changes.
 

package/schemas/config.schema.json

@@ -159,7 +159,7 @@
     "dashboard": {
       "default": {
         "enabled": false,
-        "host": "127.0.0.1",
+        "host": "0.0.0.0",
         "port": 9090,
         "dbPath": "./.mikrotik-mcp/events.db",
         "maxEvents": 100000,
@@ -174,7 +174,7 @@
           "type": "boolean"
         },
         "host": {
-          "default": "127.0.0.1",
+          "default": "0.0.0.0",
           "type": "string"
         },
         "port": {