Skip to main content
Glama
hemantkamalakar

Nordic Thingy:52 MCP Server

Related Servers

Alternatives to Nordic Thingy:52 MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      A comprehensive MCP server that enables AI assistants to interact with Home Assistant, control smart home devices, query states, execute services, and manage automations via natural language.
      78
      4,732
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A powerful MCP server that enables AI assistants to discover, commission, and control Matter-compatible smart home devices through a standardized interface.
      16 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connect your AI workflows to the ThingsBoard IoT Platform through this MCP server. Enables LLMs to query device telemetry, manage IoT entities (devices, assets, customers), and analyze sensor data - all through natural language. Perfect for building AI-powered IoT monitoring, predictive maintenance,
      98
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 25 tools

    Disambiguation4/5

    Each sensor read maps to a distinct physical output, and connection, LED, and sound tools are clearly separated. Minor overlap exists where read_all_sensors duplicates individual sensor reads and beep is effectively play_sound with a fixed preset, but the descriptions disambiguate these cases adequately.

    Naming Consistency4/5

    The naming is mostly consistent: read_* for sensor data, set_* for LED actions, and connect/disconnect/scan for device lifecycle. Minor deviations such as get_device_status using get instead of read, turn_off_led instead of set_led_off, and the bare beep prevent a perfect score.

    Tool Count3/5

    At 25 tools, the server sits at the heavy end and feels somewhat bulky for an MCP surface, though the count is largely justified by the device's many distinct sensors and peripherals. Convenience tools like beep and read_all_sensors add mild redundancy and could be consolidated without losing functionality.

    Completeness3/5

    The server covers connection management, environmental and motion sensing, LED control, and preset sound playback well. However, the Nordic Thingy:52's physical button is not exposed, and the description mentions frequency-based sound with volume control but no such tool exists, leaving notable device capabilities unimplemented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues