Skip to main content
Glama
brennanreamer

MQTT MCP Server

by brennanreamer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MQTT MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • OMNI-MQTT-MCP

      Omniscience-Labs
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to publish and subscribe to MQTT topics with configurable transport options (STDIO, Streamable HTTP, SSE), supporting both local development and web deployments with flexible broker authentication.
      2
      MIT

    • MQTT-Bridge

      rsbohn
      F
      license
      Not graded
      quality
      C
      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.
      -

    • mqtt-mcp-server

      Schimmilab
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query MQTT message history stored in SQLite, including topic inventories, last values, historical data, silent devices, and collector connection gaps. Supports publishing messages when write mode is enabled.
      8
      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.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct MQTT operation: subscribe, unsubscribe, publish, read buffered messages, and list active subscriptions. The read and list tools are clearly separated by their descriptions, and no two tools appear to do the same thing.

    Naming Consistency4/5

    All tool names use the mqtt_ prefix and snake_case, which is highly consistent. The only minor deviation is that some names include an explicit object (read_messages, list_subscriptions) while others rely on implicit context (subscribe, unsubscribe, publish), but the pattern remains predictable.

    Tool Count5/5

    Five tools is well-scoped for an MQTT interaction server, covering the essential subscribe, unsubscribe, publish, read, and list operations without unnecessary bloat. Each tool earns its place and the set feels complete for typical messaging tasks.

    Completeness4/5

    The core MQTT lifecycle is covered: subscribe, unsubscribe, publish, read buffered messages, and list subscriptions. Minor gaps exist, such as no explicit tool to clear buffered messages or manage connection state, but these are workaround-able or handled outside the tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources