REST Server
The REST Server plug-in can be used to provide APIs that are accessible from outside the OPC Router.

The following properties can be configured for the REST server:
Rest Server
| Name | Description |
|---|---|
| Name | Any name under which the REST server appears in the connection project. Choose a name that is unique to you during connection projecting. |
| Provide API via web management endpoint | If this option is enabled, the port of the OPC Router Web Management is used to provide the API in addition to the selected port. |
| Port | The port on which the API should be accessible. Note:
|
| Route prefix | The prefix that must be specified after the IP address and port to reach the API. |
| Send errors as a response | If this option is enabled, the status code is sent as a response when an error occurs. |
| Always send status code | The status code is always sent, e.g., in the case of a successful transfer. |
| Authentication | Specify how to authenticate externally:
|
| Username (available with Basic authentication method) | Username for login. |
| Password (available with Basic authentication method) | Password for login. |
| SSL | If this option is active, SSL is used for the connection. |
| SSL certificate (available when SSL is enabled) | Certificate to be used for connections. The plus sign is used to add a certificate, the trash can to remove a certificate. The eye icon can be used to view the properties of the selected certificate. |
| Provide OpenAPI data | Enable this option if you want to provide OpenAPI data. This is done in the form of a JSON file. |
MCP server
| Property | Description |
|---|---|
| Enable MCP | This setting enables MCP for the REST server. |
| Authentication | There are two options for authentication: None: No authentication for MCP Bearer Token: MCP is secured with bearer token authentication. |
| Route Prefix | Route prefix for the MCP endpoint |
| Bearer Token | The bearer token for authentication with bearer tokens can be configured here. |