muav_gui_mcp

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 henry@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

  1. Send Commands

    Execute various commands on UAV devices

  2. Mission Control

    Load and start missions on UAVs

  3. Gimbal Control

    Precise control of camera gimbal positioning

  4. Task Management

    Send inspection tasks to Ground Control Station

  5. Command Discovery

    Get available commands for devices

Weather MCP Server

This is a sample MCP Server in TypeScript implementing weather tools with mock responses. It can be used as a scaffold for your own MCP Server. It includes the following features:

  • Weather Tool: A tool that provides mocked weather information based on the given location.
  • 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 Weather MCP Server template

Prerequisites

To run the MCP Server in your local dev machine, you will need: Node.js

  1. Open VS Code Debug panel. Select Debug in Agent Builder or 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.

Congratulations! You have successfully run the Weather MCP Server in your local dev machine via Agent Builder as the MCP Client. DebugMCP

What's included in the template

Folder / FileContents
.vscodeVSCode files for debugging
.aitkConfigurations for AI Toolkit
srcThe source code for the weather mcp server

How to debug the Weather 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 ModeDescriptionSteps to debug
Agent BuilderDebug 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 SSEDebug 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 STDIODebug 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 ModePortsDefinitionsCustomizationsNote
Agent Builder3001Edit , , , to change ports and parameters.N/A
MCP Inspector for SSE3001 (Server); 5173 and 3000 (Inspector)Edit , , , to change above ports.N/A
MCP Inspector for STDION/AN/AWhen 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.

Feedback

If you have any feedback or suggestions for this template, please open an issue on the AI Toolkit GitHub repository