Skip to main content
Glama
jettydiot

@jettyd/mcp

by jettydiot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @jettyd/mcp

No user-submitted related servers found.

    Related Servers

    • mcp2mqtt

      swesmith-repos
      A
      license
      B
      quality
      Not graded
      maintenance
      An MCP server that bridges the physical world and AI models by enabling natural language control of IoT hardware via the MQTT protocol. It supports real-time device monitoring, command publishing, and response handling for seamless integration between AI clients and physical devices.
      3
      MIT

    • xiaozhi-mcp-bridge-template

      kamilersz
      A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server enables AI models to interact with ESP32 devices, providing built-in tools for web search, note management, calculator, and custom tools like todo lists and timers.
      MIT

    • bus-mcp

      Pan-Robotics
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Raspberry Pi peripheral bus access, enabling AI agents to interact with CAN, I2C, SPI, UART, and GPIO directly through natural language.
      2
      MIT

    • OmniMCP

      gautham-sai05
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to discover, monitor, and control industrial hardware like ESP32 machine controllers and inspection cameras through a standardized MCP interface.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of device interaction: listing devices, reading current state, sending commands, fetching historical data, and managing automation rules. No two tools have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_devices, read_device, send_command, get_telemetry, push_rules). Predictable and uniform.

    Tool Count5/5

    5 tools is well-scoped for an IoT device management server, covering essential operations without redundancy or bloat.

    Completeness4/5

    The set covers listing, reading, commanding, telemetry, and rule automation, which are core for IoT interaction. Device create/update/delete are absent but likely outside the server's scope of managing existing devices.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources