Skip to main content
Glama
Omniscience-Labs

OMNI-MQTT-MCP

by Omniscience-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OMNI-MQTT-MCP

No user-submitted related servers found.

    Related Servers

    • MQTT MCP Server

      eduard256
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to MQTT brokers for smart home automation and IoT device control, enabling topic discovery, sensor reading, command sending, and event monitoring.
      2
      MIT

    • MQTT-Bridge

      rsbohn
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MQTT communication capabilities for Large Language Models and other clients, enabling connections to MQTT brokers, publishing and subscribing to topics, and managing real-time messaging workflows.
      -

    • MCP MQTT Server

      tspspi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to interact with MQTT brokers through publish, subscribe, and query operations. Provides fine-grained topic permissions with wildcard support for secure IoT device communication and sensor data access.
      1
      BSD 3-Clause
    • Coreflux MCP Server by CorefluxCommunity

      Coreflux MCP Serverofficial

      CorefluxCommunity
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude and other MCP-compatible AI assistants to a Coreflux MQTT broker, enabling them to discover and execute Coreflux commands for managing models, actions, rules, and routes through natural language.
      5
      Apache 2.0

    • 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.
      24
      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

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: mqtt_publish sends messages to a topic, while mqtt_subscribe receives messages from a topic. There is no overlap in functionality, and an agent can easily tell them apart based on their names and descriptions.

    Naming Consistency5/5

    Both tools follow a consistent mqtt_verb pattern (mqtt_publish and mqtt_subscribe), which clearly indicates they belong to the MQTT domain. The naming is predictable and readable throughout the set.

    Tool Count2/5

    With only 2 tools, the server feels thin for an MQTT domain, which typically involves operations like connect, disconnect, list topics, or manage brokers. While publish and subscribe are core, the lack of other essential functions limits its scope and utility.

    Completeness2/5

    The tool set is severely incomplete for MQTT operations. It lacks basic functionality such as connecting to/disconnecting from a broker, listing topics, or managing subscriptions beyond a single call. This will cause agent failures when trying to perform common MQTT workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources