Skip to main content
Glama

MQTT MCP Server

An MCP (Model Context Protocol) server that enables Cursor to read messages from an MQTT broker.

Features

  • Subscribe to MQTT topics (supports wildcards + and #)

  • Read buffered messages from subscribed topics

  • List active subscriptions

  • Configurable message buffer size

Related MCP server: OMNI-MQTT-MCP

Installation

  1. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Copy .env.example to .env and configure your MQTT broker settings:

cp .env.example .env

Configuration

Edit the .env file with your MQTT broker details:

Variable

Description

Default

MQTT_BROKER_URL

MQTT broker URL (mqtt:// or mqtts://)

mqtt://localhost:1883

MQTT_USERNAME

Username for authentication

(none)

MQTT_PASSWORD

Password for authentication

(none)

MQTT_CLIENT_ID

Client ID for MQTT connection

cursor-mqtt-mcp-{timestamp}

MAX_MESSAGES_PER_TOPIC

Max messages to buffer per topic

100

Cursor Configuration

Add this MCP server to your Cursor settings (.cursor/mcp.json or global settings):

{
  "mcpServers": {
    "mqtt": {
      "command": "node",
      "args": ["C:/path/to/mqtt-mcp/dist/index.js"],
      "env": {
        "MQTT_BROKER_URL": "mqtt://your-broker:1883",
        "MQTT_USERNAME": "your_username",
        "MQTT_PASSWORD": "your_password"
      }
    }
  }
}

Alternatively, if using a .env file in the project directory:

{
  "mcpServers": {
    "mqtt": {
      "command": "node",
      "args": ["C:/path/to/mqtt-mcp/dist/index.js"],
      "cwd": "C:/path/to/mqtt-mcp"
    }
  }
}

Available Tools

mqtt_subscribe

Subscribe to an MQTT topic to start receiving messages.

Parameters:

  • topic (required): The MQTT topic to subscribe to

  • qos (optional): Quality of Service level (0, 1, or 2). Default: 0

Example:

Subscribe to "sensors/temperature"
Subscribe to "devices/+/status" (single-level wildcard)
Subscribe to "home/#" (multi-level wildcard)

mqtt_unsubscribe

Unsubscribe from an MQTT topic.

Parameters:

  • topic (required): The MQTT topic to unsubscribe from

mqtt_read_messages

Read buffered messages from subscribed topics.

Parameters:

  • topic (optional): Specific topic to read from. If omitted, reads from all topics

  • limit (optional): Maximum messages to return. Default: 10

  • clear (optional): Clear buffer after reading. Default: false

mqtt_list_subscriptions

List all active subscriptions and their message counts.

Parameters: None

Usage Example

  1. First, subscribe to a topic:

    "Subscribe to the MQTT topic sensors/temperature"

  2. Wait for messages to arrive, then read them:

    "Read the latest messages from sensors/temperature"

  3. Check all active subscriptions:

    "List my MQTT subscriptions"

  4. Unsubscribe when done:

    "Unsubscribe from sensors/temperature"

License

MIT

Available Tools

5 tools
mqtt_list_subscriptionsB

List all active MQTT topic subscriptions and their message counts.

Inputs: no named parameters.

mqtt_publishB

Publish a message to an MQTT topic. Useful for sending test data or triggering actions on the broker.

Inputs: topic (required), message (required), qos, retain.

mqtt_read_messagesA

Read buffered messages from a subscribed topic. Returns the most recent messages received since subscribing. Supports MQTT wildcards: '+' for single level, '#' for multi-level (e.g., 'sensors/#' returns messages from all topics under 'sensors/').

Inputs: clear, limit, topic.

mqtt_subscribeB

Subscribe to an MQTT topic to start receiving messages. Supports MQTT wildcards: '+' for single level, '#' for multi-level.

Inputs: topic (required), qos.

mqtt_unsubscribeB

Unsubscribe from an MQTT topic to stop receiving messages.

Inputs: topic (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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 recent community issues

    Related MCP Connectors

    Related MCP Servers

    • 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.
      13 PyPI
      2
      BSD 3-Clause
    • 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