arpoma16/muav_gui_mcp
3.2
If you are the rightful owner of muav_gui_mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
The MultiUAV GUI MCP Server provides standardized access to MultiUAV GUI functionality, enabling LLMs to interact with UAV devices, missions, and flight data.
Tools
5
Resources
0
Prompts
0
MUAV-GCS MCP Server
MCP Server in TypeScript implementing MUAV-GCS tools that connect to Multi-UAV GCS. It includes the following features:
- MUAV-GCS Tool: A tool that provides control and access to the UAV in the MUAV-GCS System.
- Connect to Agent Builder: A feature that allows you to connect the MCP server to the Agent Builder for testing and debugging.
- Debug SSE in MCP Inspector: A feature that allows you to debug the MCP Server using the MCP Inspector.
- Debug STDIO in MCP Inspector: A feature that allows you to debug the MCP Server using the MCP Inspector.
Get started with the MUAV-GCS MCP Server template
Prerequisites
To run the MCP Server in your local dev machine, you will need: Node.js
- Open VS Code Debug panel. Select
Debug in Agent Builderor pressF5to start debugging the MCP server. - Use AI Toolkit Agent Builder to test the server with . Server will be auto-connected to the Agent Builder.
- Click
Runto test the server with the prompt.
Congratulations! You have successfully run the MUAV-GCS MCP Server in your local dev machine via Agent Builder as the MCP Client.
What's included in the template
| Folder / File | Contents |
|---|---|
.vscode | VSCode files for debugging |
.aitk | Configurations for AI Toolkit |
src | The source code for the mcp server |
How to debug the MUAV-GCS MCP Server
Notes:
- MCP Inspector is a visual developer tool for testing and debugging MCP servers.
- All debugging modes support breakpoints, so you can add breakpoints to the tool implementation code.
| Debug Mode | Description | Steps to debug |
|---|---|---|
| Agent Builder | Debug the MCP server in the Agent Builder via AI Toolkit. | 1. Open VS Code Debug panel. Select Debug in Agent Builder and press F5 to start debugging the MCP server.2. Use AI Toolkit Agent Builder to test the server with . Server will be auto-connected to the Agent Builder. 3. Click Run to test the server with the prompt. |
| MCP Inspector for SSE | Debug the MCP server using the MCP Inspector. | 1. Open VS Code Debug panel. Select Debug SSE in Inspector (Edge) or Debug SSE in Inspector (Chrome). Press F5 to start debugging.2. When MCP Inspector launches in the browser, click the Connect button to connect this MCP server.3. Then you can List Tools, select a tool, input parameters, and Run Tool to debug your server code. |
| MCP Inspector for STDIO | Debug the MCP server using the MCP Inspector. | 1. Open VS Code Debug panel. Select Debug STDIO in Inspector. Press F5 to start debugging.2. When MCP Inspector launches in your default browser, click the Connect button to connect this MCP server.3. Then you can List Tools, select a tool, input parameters, and Run Tool to debug your server code.4. Of course, you can add breakpoint to the tool implementation code. |
Default Ports and customizations
| Debug Mode | Ports | Definitions | Customizations | Note |
|---|---|---|---|---|
| Agent Builder | 3001 | Edit , , , to change ports and parameters. | N/A | |
| MCP Inspector for SSE | 3001 (Server); 5173 and 3000 (Inspector) | Edit , , , to change above ports. | N/A | |
| MCP Inspector for STDIO | N/A | N/A | When launching debugging, it launches MCP Inspector with MCP settings pre-configured (default to npm --silent run dev:stdio). After clicking Connect, Inspector launches MCP server on STDIO, which is also auto-attached for debugging via VSCode. |