---
title: "Direct MQTT Connector"
slug: "direct-mqtt-connector"
status: "new"
updated: 2026-09-18T17:05:44Z
published: 2026-09-18T17:05:49Z
canonical: "learn.servitly.com/direct-mqtt-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://learn.servitly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Direct MQTT Connector

Servitly includes an MQTT Broker that you can use to establish a direct connection with your products. To use it, select the **Servitly Thing Connector** (STC) within the *Connection* configuration tab.

## Connection Configuration

Within the *Connection* tab, under the editing page of a customer, location, or thing, you can configure the *Servitly Thing Connector* by providing the following credentials (generated by you):

- **Username**: The unique username used to open the MQTT connection.
- **Password**: The password requested during the MQTT channel authentication; it must be at least 8 characters long, and it must contain at least one lowercase letter, one uppercase letter, and one number.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(329).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A32%3A33Z&se=2026-10-16T18%3A32%3A33Z&sr=c&sp=r&sig=NQh0US2hSLwjkCdVEHb2ytFG274FIKpZ%2BR%2FKxh5BmN8%3D)

Moreover, it is possible to specify the payload format; by default, only *JSON* is available, but depending on the enabled plugins (e.g., [Asem](https://help.servitly.com/hc/en-us/articles/9818174436380)), it is possible to use other formats. The Connection tab is available on the Location and Customer level, and the configured IoT connector is inherited by the sublevels. In this way, you can configure an IoT connection for a single thing, a single location, or an entire customer.

## Thing Connection Mapping

At the thing level, in the *Connection* tab, you can configure the specific mapping for the thing.

![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(330).png?sv=2026-02-06&spr=https&st=2026-10-16T17%3A32%3A33Z&se=2026-10-16T18%3A32%3A33Z&sr=c&sp=r&sig=NQh0US2hSLwjkCdVEHb2ytFG274FIKpZ%2BR%2FKxh5BmN8%3D)

- **Asset Id***:* The unique asset identifier of the device.
- **Path***:* The optional path you can use for more structured MQTT topics, needed when the same gateway is managing multiple things. In this case, the Asset Id will identify the gateway; instead, the thing is identified by the Path.

IoT Connector Username, *Asset Id,* and *Path* are used to compute the full topic for metric publishing and subscribing.

```http
<USERNAME>/<THING_MAPPING_ASSET_ID>/<THING_MAPPING_PATH>/<METRIC_PATH>
```

## Publishing Limits

Connected products can publish data at a limited rate; for more details, refer to the [Publishing Rate Limit](/docs/publishing-rate-limit) article.