Skip to main content
Glama
nomos-system

nomos MCP Bridge

Official
by nomos-system

Related Servers

Alternatives to nomos MCP Bridge

No user-submitted related servers found.

    Related Servers

    • 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.
      20 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that lets AI assistants list and control home devices — lights, air conditioners, cameras, speakers, plugs and scheduled tasks — across Xiaomi (Mi Home), Tuya, Midea, eWeLink (Sonoff) and Huawei SmartHome using accounts you authorize on your own machine. It binds to localhost only and communicates with each vendor cloud, so agents can act on devices through natural language.
      28 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI assistants to control Home Assistant via natural language, including device control, automation management, and system configuration.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language control of Loxone smart home systems, including lighting, audio, climate, and environmental monitoring, through MCP-compatible clients.
      31 npm
      2
      AGPL 3.0
    • A
      license
      B
      quality
      A
      maintenance
      MCP server for OpenClaw that enables AI clients to control smart home devices, manage memory and cron jobs, and orchestrate multiple AI sub-agents.
      37
      52 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI agents to control Xiaomi Mi Home smart devices through natural language, with support for listing devices, controlling properties, and running scenes.
      MIT

    TDQS

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: adding, removing, selecting, listing controllers, checking connection status, and opening setup. No two tools overlap in functionality.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., add_controller, list_controllers), but 'connection_status' is a noun_noun form, slightly deviating from the pattern.

    Tool Count5/5

    With 6 tools, the server is well-scoped for managing controller registrations and connections, covering essential operations without unnecessary bloat.

    Completeness4/5

    The tool set covers core CRUD for controllers (add, remove, list, select) plus connection status and setup. A minor gap is the lack of an explicit disconnect tool, though select_controller handles it implicitly.

    Maintenance

    ActivityActive
    ResponsivenessNo issues