# Cybus::Server

A *server* resource describes an additional server that provides data to clients. External clients may connect to this server, and receive data from or provide data to the server.

Connectware already includes a MQTT broker which makes all data available in the internal MQTT API. Additional *server* resources can offer more choices to access the data, such as through OPC UA or RESTful interaction.

The data in the server resource is organized in terms of [node](/1-7-2/documentation/services/structure-of-commissioning-files/resources/cybus-node.md) resources, which are defining the available data in a hierarchical tree structure.

Currently, the following concrete server is available (in addition to Connectware’s MQTT broker):

* [OPC UA Server](/1-7-2/documentation/industry-protocol-details/opc-ua/opc-ua-server.md)

## Common Properties

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

#### targetState

The state this resource should be in, after start-up.

* is optional
* type: `enum`, must be one of `enabled`, `disabled`
* default: `enabled`

## Custom Properties

Depending on the protocol type of the server, additional custom properties are available:

* [Cybus::Server::Opcua](/1-7-2/documentation/industry-protocol-details/opc-ua/opc-ua-server.md#custom-server-properties)


---

# Agent Instructions: 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:

```
GET https://docs.cybus.io/1-7-2/documentation/services/structure-of-commissioning-files/resources/cybus-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.