No user-submitted related servers found.
Scored across 40 tools
Each tool maps to a distinct resource/action: CRUD for devices, applications, profiles, and gateways are clearly separated, and session/queue/capture operations have unique names. Where two tools could overlap (wait_for_event vs device_recent_events, device_activate vs device_set_keys), the descriptions explicitly distinguish them.
The overwhelming majority follow a consistent lowercase snake_case resource_action pattern (device_list, application_update, gateway_delete, capture_start). Minor deviations such as server_info and wait_for_event are understandable but break the strict verb_noun/resource_action convention enough to prevent a perfect score.
40 tools is well beyond the heavy range and will impose a significant selection burden on an agent, even though the tools are organized by domain. The breadth is justified by ChirpStack's API surface, but for an MCP tool set it is too many to be considered well-scoped.
The set covers full CRUD/lifecycle for devices, applications, profiles, and gateways plus key device operations (activation, queueing, metrics, captures, events). Minor gaps exist such as tenant listing and per-item downlink queue deletion, but core workflows are not blocked.