Skip to main content
Glama
Sign In
IoT Device Management MCP Server

IoT Device Management MCP Server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to IoT Device Management MCP Server

No user-submitted related servers found.

    Related Servers

    • esp32-mcp

      StefanYasin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to control an ESP32 board's relays, GPIO pins and analog sensors over a small HTTP API on the local network, with no cloud service in the middle.
      5
      MIT

    • OmniButler

      Tiybai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover, read and control smart-home devices from multiple vendors through a unified capability model, and to author and trigger YAML scenes that a local deterministic engine executes without the AI in the control loop. High-risk actions such as door locks and garage doors are held in a confirmation queue for a human, and every call is written to a local audit log.
      Apache 2.0

    • ClawMem MCP Server

      BFLabsAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.
      416 npm
      MIT

    • NWO Robotics

      RedCiprianPater
      A
      license
      B
      quality
      D
      maintenance
      Control real robots and IoT devices through AI agents. Self-register with wallet authentication, pay with ETH for tier upgrades, and execute Vision-Language-Action commands. Features robot control, sensor monitoring, multi-agent coordination, and autonomous payments.
      8
      1
      MIT

    • Larnitech MCP

      mpopovych-thinkhome
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to connect to smart-home controllers to read device snapshots, watch live state changes, look up type-specific documentation and known vendor quirks, save and compare data snapshots, and perform guarded two-phase writes for lights, climate, blinds, sensors and meters. Writes stay disabled until explicitly enabled, are previewed and token-confirmed before execution, and report what actually landed on the device.
      319 PyPI
      1
      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.6/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, though device_analytics and get_fleet_dashboard both provide overviews and could cause slight confusion. However, descriptions help differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (e.g., register_device, get_alerts, send_command) with no mixing of conventions.

    Tool Count5/5

    9 tools cover the essential IoT device management operations well, including registration, listing, status, alerts, commands, and firmware updates. Not too few or too many.

    Completeness2/5

    Missing crucial device lifecycle operations: no update_device to modify attributes (e.g., location, name) and no delete_device to remove devices. These gaps can cause agent failures when managing device lifecycles.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources