> 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/documentation/services/service-commissioning-files/resources/cybus-server.md).

# Cybus::Server

The **Cybus::Server** resource defines an additional server endpoint that makes data available to external clients. External applications or devices can connect to this server to either consume data from Connectware or provide data into it.

By default, Connectware already includes an internal MQTT broker ([CybusMQ](/broker/cybusmq.md)), which exposes all data via the internal MQTT API. The Cybus::Server resource allows you to extend this by offering other standardized access methods, such as OPC UA or RESTful APIs.

The data exposed by a server is structured through [Cybus::Node](/documentation/services/service-commissioning-files/resources/cybus-node.md) resources, which define available data points in a hierarchical tree. This ensures a clear and consistent data model regardless of the chosen protocol.

In addition to the internal MQTT broker, the [OPC UA Server](/connectors/servers/opc-ua-server.md) is available.

## Server Properties

| Property                    | Type   | Required |
| --------------------------- | ------ | -------- |
| [targetState](#targetstate) | `enum` | Optional |

### targetState

Specifies the operational state of the server after Connectware startup.

* **Optional**
* Type: `enum`
* Allowed values:
  * `enabled` - The server will be started automatically (default).
  * `disabled` - The server will remain stopped until explicitly enabled.
* Default: `enabled`

## Custom Server Properties

Each server type may define additional properties specific to its protocol. For example:

* [Cybus::Server::Opcua](/connectors/servers/opc-ua-server.md#custom-server-properties)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybus.io/documentation/services/service-commissioning-files/resources/cybus-server.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.