MQTT (Message Queuing Telemetry Transport)

MQTT is a lightweigth protocol for M2M communications. Original version had been proposed by IBM and Eurotech. Protocol standardisation is now being handled by the OASIS standard development organisation. Extracted from the OASIS website: The standard supports bi-directional messaging to uniformly handle both signals and commands, deterministic message delivery, basic QoS levels, always/sometimes-connected scenarios, loose coupling, and scalability to support large numbers of devices.  As an M2M/Internet of Things (IoT) connectivity protocol, MQTT is designed to support messaging transport from remote locations/devices involving small code footprints (e.g., 8-bit, 256KB ram controllers), low power, low bandwidth, high-cost connections, high latency, variable availability, and negotiated delivery guarantees. For example, MQTT is being used in sensors communicating to a broker via satellite links, SCADA, over occasional dial-up connections with healthcare providers (medical devices), and in a range of home automation and small device scenarios. MQTT is also ideal for mobile applications because of its small size, minimized data packets, and efficient distribution of information to one or many receivers (subscribers).  
  • Latest version ID: v3.1
  • Tags: , ,
  • Latest update: August 5, 2014
  • Developed by: OASIS (Organization for the Advancement of Structured Information Standards)
  • Contact name:
    • COMPOSE MobileSDK (more details)
      • Relation type: Re-use relationship
      • Validation:
      • Completeness of the relation: %
      • PAHO Eclipse Project (more details)
        • Relation type: Re-use relationship
        • Validation:
        • Completeness of the relation: %
        • ServIoTicy - IoT Streaming Made Easy (more details)
          • Relation type: Re-use relationship
          • Validation:
          • Completeness of the relation: 50%
          • Node-RED: A visual tool for wiring the Internet of Things (more details)
            • Relation type: Interoperability relationship
            • Validation: Avalaible MQTT flows: 1-wire to MQTT bridge Weather reports to SMS and MQTT topic MQTT-SN buffer formatter Owntracks Geofence Notifications via Pushover Pinoccio Command Flow UDP Request response Tweet your location with MQTTitude Sensor hub for JeeNode / Open Energy Monitor Parsing JeeNode Room Board Flow that makes a new flow Turn off HDMI connected TV when leaving WIFI + presence dashboard rain prediction Simple Twilio based IVR
            • Completeness of the relation: %

        Intellectual property rights (IPR)

        The OASIS MQTT Technical Comittee (TC) shall operate under Non Assertion Terms.

        Non-assertion covenants ensure that organizations or individuals who participate in writing a standard cannot demand royalty or exercise license rights against users or implementors of such approved standards. Qualifying participants or contributors automatically make Non-Assertion Covenants when they work in an OASIS Technical Committee that operates under this new IPR mode.


Download 3.1 version from IBM website: PDF download of MQTT V3.1 protocol specification

Service level


The OASIS MQTT Security Subcommittee provides guidance on how MQTT solutions may be made secure and how this may mesh with existing security standards.

Their work is based on the NIST Cybersecurity Framework: