Feature Request: Add pagination to the NinjaOne integration via Super Magic MCP Server tools (and surface OS in the device list payload)

Summary

The NinjaOne integration in Thread MCP currently cannot support estate-wide device queries because its list tools do not paginate and the device search payload omits OS data. Both capabilities already exist in NinjaOne's underlying public API — this is a surfacing gap, not a new capability.

Affected tools

search_ninjaone_devices

list_ninjaone_organizations

Current verified limitations (observed in live testing)

search_ninjaone_devices returns a hard maximum of 25 results per call with no pagination (no page token / cursor / offset). Unscoped searches truncate at 25 devices.

list_ninjaone_organizations caps at 25 organizations and pads/truncates — it cannot enumerate all orgs.

OS name and build number are not included in the device search payload; retrieving OS requires one get_ninjaone_device call per device.

Net effect: any estate-wide query (e.g. "find all Windows Server 2012 / 2012 R2 across all clients") requires walking org IDs blindly, then making one detail call per device — potentially hundreds of calls across dozens of sessions. It is practically infeasible.

Requested changes:

Add cursor/page-token pagination to search_ninjaone_devices and list_ninjaone_organizations. NinjaOne's public API already supports paging on /v2/devices and /v2/organizations.

Include os.name and os.buildNumber in the device list/search payload. The source /v2/devices endpoint already returns these fields, so exposing them eliminates the per-device detail fan-out at near-zero cost.

Business justification

These two changes convert multi-session, manual estate sweeps into a few paged calls. Primary use cases: end-of-life OS inventory (Server 2012/2012 R2, Win10 EOL), vulnerability/compliance reporting, and fleet-wide software/OS census. NinjaOne is the universal RMM across all our clients, and it is the source of truth for live device state — PSA ConfigurationItems are not a reliable substitute due to duplicates and stale records. This makes accurate Ninja-side enumeration essential.

Priority: High — blocks all estate-wide device/OS reporting through the integration.