idm-mcp
Related Servers
Alternatives to idm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and HTTP callers to configure servers and devices, run commands, and read real output from a running network simulation through a shared gateway.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to inspect a sanitized router endpoint catalog, read DHCP and Wi-Fi data, and perform explicitly confirmed configuration writes or UPnP SOAP actions under configurable safety gates.9MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to manage a self-hosted RPort fleet by listing and inspecting connected devices, opening and closing SSH tunnels, and executing commands through RPort agents.10MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to securely reach and invoke tools on self-hosted machines through a remote gateway, using outbound-only device connections, OAuth or bearer authentication, per-device policies, and audit logging.8 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to access a local computer through a controlled, permission-based tool surface for read-only or developer-mode file, process, and terminal operations.6MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to read facilities, devices, live values, history, and alarms from a Cloud Studio Gear IoT account, filtered to the user's permissions and strictly read-only.6MIT
TDQS
Scored across 14 tools
Most tools target distinct resources (devices, connections, streams, activity, history), and the parameter-reading family (list_parameters, get_parameters, get_value, get_structure) is differentiated by descriptions. However, the four parameter tools plus the topology trio (get_protocols, get_streams, list_connections) require careful reading to avoid misselection.
All tools share the idm_ prefix and follow a mostly consistent verb_noun pattern (list_devices, get_parameters, read_stream, get_history). Minor deviations: idm_gateway_info and idm_device_status are noun-only, and get vs read both appear but are used sensibly.
14 tools is well-scoped for a gateway/device management server, covering topology, parameters, streams, and history without obvious redundancy. Each tool earns its place.
The read surface is thorough (info, devices, connections, streams, parameters, history), but the descriptions reference write tools and idm_open_stream that are not present in the tool list, implying missing write capability. The surface is read-only despite describing a read/write parameter workflow.