Universal Device MCP
Related Servers
Alternatives to Universal Device MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables AI agents to discover and manage embedded boards, and perform serial communication through a TCP gateway, supporting commands, logs, and transactional exchanges.20-
- AlicenseNot gradedqualityBmaintenanceEnables agents to discover devices, query their capabilities, invoke system calls, and stage resources or deliver apps to connected WishOS hardware through a self-hosted connector and relay. It routes device-initiated tasks into an existing harness session (Codex, Claude Code, and others), keeping inference, tools, and history with that agent while handling voice, interface, and app transfer to the device.MIT
- AlicenseNot gradedqualityCmaintenanceEnables cloud LLM agents to discover and invoke physical hardware on edge and IoT devices through standard MCP tools, bridging constrained device channels like UART, BLE, and Wi-Fi.3MIT
- AlicenseAqualityCmaintenanceGives AI agents direct hands-on access to physical hardware and host OS resources over local stdio: serial monitoring with crash-dump detection, firmware compile/flash via arduino-cli, PlatformIO, ESP-IDF and esptool, direct GPIO/I2C/SPI over FTDI bridges, BLE GATT operations, webcam or microscope snapshots, logic analyzer captures, audio recording and test tones, GUI screenshots and hotkeys, and Android ADB commands. It also helps diagnose toolchain and serial-permission problems and identify or terminate processes that lock a port.33MIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage MicroPython and CircuitPython boards over USB, including listing boards, browsing and editing files, running Python code, resetting boards, and installing firmware.14491 npm10MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to communicate with UART/serial devices, offering tools for port management, data read/write, and protocol handling.1MIT
TDQS
Scored across 20 tools
Most tools have clearly distinct targets: discovery, monitoring, profile management, interface sessions, and payload analysis are separable. The main overlap is between discover_devices and discover_wireless_devices, since discover_devices can also include wireless transports, and communicate/open_interface boundaries require reading descriptions carefully.
Names are consistently snake_case and mostly follow a verb_noun convention such as discover_devices, get_runtime_status, and update_device_profile. The only notable deviation is the verb-only name communicate, which is still understandable but breaks the pattern slightly.
Twenty tools is somewhat heavy but defensible for a universal device server spanning discovery, monitoring, Android wireless workflows, interface sessions, profile knowledge, and payload analysis. Each tool has a meaningful role, though the surface is larger than the typical 3-15 tool range.
The set covers the core lifecycle well: discovery, monitoring/events, device inspection, interface open/close, communication, profile CRUD/export, and knowledge retention. Minor gaps remain, such as policy mutation, granular deletion of discoveries/experiments, or a more generic device connection abstraction beyond Android wireless.