> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/broker/cybusmq/configuration.md).

# Configuring CybusMQ

Features, concepts, and configuration options for CybusMQ.

CybusMQ, the MQTT broker of Cybus Connectware, is derived from VerneMQ and inherits most of its capabilities. This documentation introduces the key features and concepts of CybusMQ, highlighting what distinguishes it from VerneMQ.

For standard VerneMQ features and detailed technical documentation, refer to the [official VerneMQ documentation](https://docs.vernemq.com/1.13.0). The VerneMQ documentation covers comprehensive details on:

* General broker configuration
* Clustering setup
* Plugin configuration
* Performance tuning
* Standard authentication and authorization

The following sections detail the CybusMQ-specific configuration differences and enhancements that are unique to the Connectware ecosystem.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/broker/cybusmq/configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.