Skip to main content
Glama
emqx

AIoT MCP Server

Official
by emqx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AIoT MCP Server

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

    • 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

    • @jettyd/mcp

      jettydiot
      A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI agents direct access to IoT devices via the jettyd platform, enabling control and monitoring of ESP32 devices through natural language.
      5
      35 npm
      MIT

    • node-red-mcp

      ziv-daniel
      F
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server for Node-RED integration, enabling AI agents to manage flows, install modules, and monitor Node-RED instances via natural language.
      5
      -

    • MQTT MCP Server

      ezhuk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM agents to securely monitor and control MQTT devices for building automation, industrial control, and smart home systems through a standardized MCP interface.
      22
      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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: discover finds devices/rules, publish sends commands, query retrieves status. No overlap in functionality; the descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names are single verbs in lowercase, following a consistent imperative style (discover, publish, query). No mixing of conventions or styles.

    Tool Count5/5

    Three tools is well-scoped for an MQTT-based AIoT server, covering discovery, control, and status query. Each tool earns its place without unnecessary bloat or missing core operations.

    Completeness4/5

    The core lifecycle of discovering, controlling, and querying devices is covered. A minor gap is the lack of explicit rule management (create/update/delete), but rules are discovered via the discover tool, and the primary IoT interactions are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources