# Plugins

## Introduction

The **Plugins Module** allows the user to activate or deactivate different components within **Incari**. This provides one with the foundation for a self-scalable structure, combining creativity and functionality to ensure **Incari** supports the user's individual needs.

The **Plugins Module** looks like this when it is opened:

![](/files/hvOmGIay0Qf9izdfkUge)

## Contents

* [**Communication**](/incari-studio/2024.1/modules/plugins/communication.md)
  * [**Bluetooth**](/incari-studio/2024.1/modules/plugins/communication/bluetooth.md)
  * [**MAVLink**](/incari-studio/2024.1/modules/plugins/communication/mavlinkmanager.md)
  * [**Serial**](/incari-studio/2024.1/modules/plugins/communication/serialmanager.md)
  * [**Socket.IO**](/incari-studio/2024.1/modules/plugins/communication/socketiomanager.md)
  * [**TCP**](/incari-studio/2024.1/modules/plugins/communication/tcpconnectionsmanager.md)
  * [**UDP**](/incari-studio/2024.1/modules/plugins/communication/udpconnectionsmanager.md)
  * [**WebSocket**](/incari-studio/2024.1/modules/plugins/communication/websocket.md)


---

# 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.incari.com/incari-studio/2024.1/modules/plugins.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.
