SSyncDev

Meshtastic-mcp Server

Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP.

Local serverstdio

What is the Meshtastic-mcp Server?

Meshtastic-mcp is an MCP integration. Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP.

Packages and local setup

The published pypi package is meshtastic-mcp, version 0.3.0. Its declared MCP transport is stdio.

The package declares MESHTASTIC_FIRMWARE_ROOT: Path to a Meshtastic firmware checkout. Optional — enables the firmware capability (build/flash/boards/userprefs). Core device/admin/recorder tools work without it.; MESHTASTIC_MCP_TCP_HOST: host[:port] of a meshtasticd TCP node to surface in list_devices (default port 4403).; MESHTASTIC_MCP_TOOLSETS: Comma-separated tool groups to expose: core, firmware, hardware, android, discord, replay, rf, local-model. Unset or 'all' exposes every group; a hidden tool cannot be called.; MESHTASTIC_MCP_READ_ONLY: Set to 1 to hide every tool that can change device or host state.; MESHTASTIC_MCP_CONFIRM: Confirmation policy for destructive tools. 'agent' runs a tool called with confirm=True; 'human' asks the user through elicitation before an irreversible tool (factory_reset, erase_and_flash, nrf52_factory_erase, vanity_apply, destructive esptool/nrfutil/picotool calls) even when confirm=True is passed.; MESHTASTIC_MCP_DATA_DIR: Directory for recorder JSONL logs and persistent data. Defaults to platformdirs user-data-dir, then cwd. Set this to keep recorder data in a known location.; MESHTASTIC_UI_CAMERA_DEVICE: Camera device index or path for capture_screen (default: 0). Role-specific overrides: MESHTASTIC_UI_CAMERA_DEVICE_TESTER, _DUT, etc.; MESHTASTIC_UHUBCTL_LOCATION_TESTER: uhubctl USB hub location for the TESTER role port (e.g. '1-1'). Enables uhubctl_power/uhubctl_cycle against that role. Suffix varies by role: _DUT, _RELAY, etc.; MESHTASTIC_PIO_BIN: Path to the PlatformIO CLI binary. Searched in order: this env var, ~/.platformio/penv/bin/pio, then PATH. Only needed if PlatformIO is not on PATH.; MESHTASTIC_ANDROID_ROOT: Path to a Meshtastic-Android source checkout (directory containing gradlew). Optional — enables building the APK from source via scripts/build_android_apk.sh. If unset, scripts default to cloning fresh or using a release APK.; MESHTASTIC_APPLE_ROOT: Path to a Meshtastic-Apple source checkout (directory containing Meshtastic.xcworkspace). Optional — enables building the iOS Simulator .app from source via scripts/build_apple.sh. If unset, scripts clone fresh..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
MESHTASTIC_FIRMWARE_ROOTPath to a Meshtastic firmware checkout. Optional — enables the firmware capability (build/flash/boards/userprefs). Core device/admin/recorder tools work without it.Check documentation
MESHTASTIC_MCP_TCP_HOSThost[:port] of a meshtasticd TCP node to surface in list_devices (default port 4403).Check documentation
MESHTASTIC_MCP_TOOLSETSComma-separated tool groups to expose: core, firmware, hardware, android, discord, replay, rf, local-model. Unset or 'all' exposes every group; a hidden tool cannot be called.Check documentation
MESHTASTIC_MCP_READ_ONLYSet to 1 to hide every tool that can change device or host state.Check documentation
MESHTASTIC_MCP_CONFIRMConfirmation policy for destructive tools. 'agent' runs a tool called with confirm=True; 'human' asks the user through elicitation before an irreversible tool (factory_reset, erase_and_flash, nrf52_factory_erase, vanity_apply, destructive esptool/nrfutil/picotool calls) even when confirm=True is passed.Check documentation
MESHTASTIC_MCP_DATA_DIRDirectory for recorder JSONL logs and persistent data. Defaults to platformdirs user-data-dir, then cwd. Set this to keep recorder data in a known location.Check documentation
MESHTASTIC_UI_CAMERA_DEVICECamera device index or path for capture_screen (default: 0). Role-specific overrides: MESHTASTIC_UI_CAMERA_DEVICE_TESTER, _DUT, etc.Check documentation
MESHTASTIC_UHUBCTL_LOCATION_TESTERuhubctl USB hub location for the TESTER role port (e.g. '1-1'). Enables uhubctl_power/uhubctl_cycle against that role. Suffix varies by role: _DUT, _RELAY, etc.Check documentation
MESHTASTIC_PIO_BINPath to the PlatformIO CLI binary. Searched in order: this env var, ~/.platformio/penv/bin/pio, then PATH. Only needed if PlatformIO is not on PATH.Check documentation
MESHTASTIC_ANDROID_ROOTPath to a Meshtastic-Android source checkout (directory containing gradlew). Optional — enables building the APK from source via scripts/build_android_apk.sh. If unset, scripts default to cloning fresh or using a release APK.Check documentation
MESHTASTIC_APPLE_ROOTPath to a Meshtastic-Apple source checkout (directory containing Meshtastic.xcworkspace). Optional — enables building the iOS Simulator .app from source via scripts/build_apple.sh. If unset, scripts clone fresh.Check documentation