Skip to main content
Glama
Sign In
anonyme-afk

Universal Device MCP

by anonyme-afk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Universal Device MCP

No user-submitted related servers found.

    Related Servers

    • WishOS Hub

      cccat6
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • pico-bay by ctrlpi

      pico-bayofficial

      ctrlpi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      219 npm
      7
      MIT

    • mcp-uart

      SamyiHu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to communicate with UART/serial devices, offering tools for port management, data read/write, and protocol handling.
      MIT

    • mcp-serial

      HumbertoBernal
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to communicate with serial devices such as Arduinos, ESP32s, USB-UART adapters, and RS-232 instruments by discovering ports, opening connections, sending commands, reading responses, and controlling reset lines.
      12
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources