@usex/mikrotik-mcp 6.12.0 → 6.13.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.
@@ -1,7 +1,7 @@
1
1
  // @bun
2
2
  import {
3
3
  openSnapshotStore2
4
- } from "./library-he7xy22v.js";
4
+ } from "./library-2wd7mt3g.js";
5
5
  export {
6
6
  openSnapshotStore2 as openSnapshotStore
7
7
  };
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@usex/mikrotik-mcp",
3
- "version": "6.12.0",
3
+ "version": "6.13.0",
4
4
  "description": "MCP server for MikroTik RouterOS — 780+ tools over SSH for firewall, NAT, routing, DHCP, DNS, WireGuard, wireless, QoS and more.",
5
5
  "keywords": [
6
6
  "ai",
@@ -262,6 +262,8 @@
262
262
  "allowedOrigins": "",
263
263
  "corsOrigins": "",
264
264
  "toolPageSize": 0,
265
+ "toolSurface": "full",
266
+ "coreTools": "",
265
267
  "appViews": false,
266
268
  "capabilityGating": "annotate"
267
269
  },
@@ -300,6 +302,15 @@
300
302
  "minimum": 0,
301
303
  "maximum": 9007199254740991
302
304
  },
305
+ "toolSurface": {
306
+ "default": "full",
307
+ "type": "string",
308
+ "enum": ["full", "core"]
309
+ },
310
+ "coreTools": {
311
+ "default": "",
312
+ "type": "string"
313
+ },
303
314
  "appViews": {
304
315
  "default": false,
305
316
  "type": "boolean"
@@ -318,6 +329,8 @@
318
329
  "allowedOrigins",
319
330
  "corsOrigins",
320
331
  "toolPageSize",
332
+ "toolSurface",
333
+ "coreTools",
321
334
  "appViews",
322
335
  "capabilityGating"
323
336
  ],
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "format": 1,
3
- "version": "6.12.0",
3
+ "version": "6.13.0",
4
4
  "modules": [
5
5
  {
6
6
  "slug": "client-check",
@@ -1706,7 +1706,7 @@
1706
1706
  "label": "Access Scope",
1707
1707
  "group": "Discovery & Meta",
1708
1708
  "description": "Caller-scoped access control: inspect the risk/device/tool boundary enforced on this session, review denied calls, and voluntarily narrow the scope (one-way).",
1709
- "alwaysOn": false,
1709
+ "alwaysOn": true,
1710
1710
  "tools": ["get_access_scope", "narrow_access_scope"]
1711
1711
  },
1712
1712
  {
@@ -2111,7 +2111,7 @@
2111
2111
  "label": "Safe Mode",
2112
2112
  "group": "System & Ops",
2113
2113
  "description": "Transactional config window with auto-revert (Ctrl+X session).",
2114
- "alwaysOn": false,
2114
+ "alwaysOn": true,
2115
2115
  "tools": [
2116
2116
  "set_safe_mode_timeout",
2117
2117
  "safe_mode_status",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "$schema": "https://json-schema.org/draft/2020-12/schema",
3
- "version": "6.12.0",
3
+ "version": "6.13.0",
4
4
  "generated": "by scripts/gen-schemas.ts — do not edit by hand",
5
5
  "toolCount": 983,
6
6
  "tools": [
@@ -1715,7 +1715,7 @@
1715
1715
  "idempotentHint": true,
1716
1716
  "openWorldHint": false
1717
1717
  },
1718
- "description": "🔍 START HERE — this is the PRIMARY entry point for ANY MikroTik / RouterOS task. ALWAYS call this tool FIRST before attempting any other tool. This server has several hundred dedicated tools with full validation and structured output, but the host only surfaces a small subset — this tool searches the FULL catalog and finds the best match for your intent.\n\nDescribe what you want to do in natural language or keywords, e.g. 'block a LAN client by MAC', 'add an IPv4 firewall filter rule', 'import a TLS certificate', 'list DHCP leases', 'create a WireGuard peer'. Returns each match's exact tool name, description, and parameters — then call it directly if available, or via `invoke_tool`.\n\nWorkflow: find_tools → (optional) describe_tool → invoke_tool. Only fall back to run_routeros_command if this search returns zero results. For IPv4 vs IPv6, include 'ipv4' or 'ipv6' to disambiguate. For authorized changes that must be coordinated across multiple routers, search 'begin_transaction' BEFORE individual write tools (VPN tunnels, peering, routes or fleet ACLs). Discovery does not authorize verify_transaction or commit_transaction.",
1718
+ "description": "🔍 START HERE — this is the PRIMARY entry point for ANY MikroTik / RouterOS task. ALWAYS call this tool FIRST before attempting any other tool. This server has several hundred dedicated tools with full validation and structured output, but the host only surfaces a small subset — this tool searches the FULL catalog and finds the best match for your intent.\n\nDescribe what you want to do in natural language or keywords, e.g. 'block a LAN client by MAC', 'add an IPv4 firewall filter rule', 'import a TLS certificate', 'list DHCP leases', 'create a WireGuard peer'. Returns each match's exact tool name, description, parameters and a ready-to-run `invoke_tool` call.\n\nWorkflow: find_tools → (optional) describe_tool → invoke_tool. Only if this search returns zero results, run a raw command with `invoke_tool {\"name\":\"run_routeros_command\",\"arguments\":{\"command\":\"…\"}}`. For IPv4 vs IPv6, include 'ipv4' or 'ipv6' to disambiguate. For authorized changes that must be coordinated across multiple routers, search 'begin_transaction' BEFORE individual write tools (VPN tunnels, peering, routes or fleet ACLs). Discovery does not authorize verify_transaction or commit_transaction.",
1719
1719
  "inputSchema": {
1720
1720
  "$schema": "https://json-schema.org/draft/2020-12/schema",
1721
1721
  "type": "object",
@@ -1768,7 +1768,7 @@
1768
1768
  "destructiveHint": false,
1769
1769
  "openWorldHint": false
1770
1770
  },
1771
- "description": "Execute ANY tool in the catalog by its exact name with the given arguments — the precise way to run a tool you found via find_tools but the host hasn't surfaced for a direct call. The arguments are validated against that tool's real schema and run through its real handler, so this is exactly as safe/accurate as calling the tool directly (unlike raw CLI). To target a specific device in a multi-device setup, set the top-level `device` parameter on THIS call — not inside `arguments`. If validation fails you get the expected parameters back; fix and retry. For a one-off raw command with no dedicated tool, prefer run_routeros_command.",
1771
+ "description": "Execute ANY tool in the catalog by its exact name with the given arguments — the way to run a tool you found via find_tools when it is not in your tool list. The call goes through the same pipeline as a direct call: the same schema validation, access and risk checks, safety guards and audit record (saved under the target tool's own name and Tool call ID). Put the target's arguments in `arguments`, exactly as describe_tool lists them — including `reason` when the target requires it. To choose a device, set `device` on THIS call or inside `arguments`. Unknown argument names are rejected, not ignored. If validation fails you get the expected parameters back; fix and retry.",
1772
1772
  "inputSchema": {
1773
1773
  "$schema": "https://json-schema.org/draft/2020-12/schema",
1774
1774
  "type": "object",