A
licenseNot graded
qualityA
maintenanceEnables MCP clients to discover and connect over MQTT, list and invoke tools, and read resources in browser and Node.js environments.
4 npm
MIT
@nexalware/mcp
Officialby nexalware
Related Servers
Alternatives to @nexalware/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and invoke backend tools over MCP JSON-RPC while enforcing 3-legged OAuth 2.0 identity propagation, role-based access control, and protocol transcoding to REST APIs.1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceExposes approved application capabilities as stable MCP tools, enabling agents to discover and execute read-only operations by default, with optional write or destructive authority for a session.MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to search for, add, configure, enable/disable, and aggregate tools from multiple MCP servers, dynamically extending their capabilities at runtime.-
- AlicenseNot gradedqualityAmaintenanceEnables aggregation, filtering, transformation, and composition of tools from multiple MCP servers through a single proxy with tool views.5AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.4 npmMIT
TDQS
A3.5/5.0
Scored across 17 tools
Disambiguation4/5
Tools are largely distinct by resource (device vs sub-device) and action (telemetry, command, schedule). Minor overlap exists between turn_device_on/off and send_command, and between get_device_commands and get_schedule_context, but descriptions clarify the boundaries.
Naming Consistency5/5
All tool names use a consistent snake_case verb_noun pattern (get_, list_, send_, turn_, create_, update_, delete_). The only slight deviation is turn_device_on/off, but it remains readable and consistent with the overall style.
Tool Count4/5
17 tools is slightly above the ideal range but justified by the need to cover devices, sub-devices, telemetry, commands, and schedules. Each tool appears to serve a distinct purpose with no redundant operations.
Completeness4/5
The surface covers device discovery, command catalog, sending commands, telemetry (latest and history), sub-device operations, and full schedule lifecycle (create/update/delete/list/history/context). Minor gaps exist, such as no device metadata update or sub-device command catalog, but core workflows are complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues