MAVLink protocols are often designed using the client-server pattern, where vehicle-based components like the autopilot typically act as a server, responding to commands sent by a ground station "client".
Initially MAVSDK was mainly developed with the use case of a ground station in mind, so plugins implemented the client-side protocol behaviour.
However, MAVSDK can also be used for the server-side of the protocol e.g. running on a companion computer on the vehicle.
This can be used to extend the functionality "in the air", or as a bridge to a proprietary or non-MAVLink flight controller.
The plugins developed specifically for this case are usually suffixed with
These server plugins can potentially also be used to test the "non-server" plugins of MAVSDK in the future.