World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 17/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 29/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Meshtastic MCP. Follow https://mcp.popnx.com/i/meshtastic-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Meshtastic MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "meshtastic": { "command": "uvx", "args": [ "meshtastic-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Meshtastic MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
SettingsDeveloperEdit Config
{
"mcpServers": {
"meshtastic": {
"command": "uvx",
"args": [
"meshtastic-mcp"
]
}
}
}Use Meshtastic MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Meshtastic MCP or shows a Meshtastic MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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_f… · default agentMESHTASTIC_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 fre…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…Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Meshtastic MCP yet
Meshtastic MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Meshtastic MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Meshtastic MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user meshtastic -- uvx meshtastic-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Meshtastic MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user meshtastic -- uvx meshtastic-mcpYou should see Meshtastic MCP listed as connected
Use Meshtastic MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Meshtastic MCP or shows a Meshtastic MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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_f… · default agentMESHTASTIC_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 fre…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…Descriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Meshtastic MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "meshtastic": { "command": "uvx", "args": [ "meshtastic-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Meshtastic MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Meshtastic MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Meshtastic MCP or shows a Meshtastic MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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_f… · default agentMESHTASTIC_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 fre…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…Descriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Meshtastic MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "meshtastic": { "type": "stdio", "command": "uvx", "args": [ "meshtastic-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Meshtastic MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Use Meshtastic MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Meshtastic MCP or shows a Meshtastic MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
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_f… · default agentMESHTASTIC_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 fre…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…Descriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user meshtastic -- uvx meshtastic-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"meshtastic": {
"command": "uvx",
"args": [
"meshtastic-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"meshtastic": {
"command": "uvx",
"args": [
"meshtastic-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"meshtastic": {
"type": "stdio",
"command": "uvx",
"args": [
"meshtastic-mcp"
]
}
}
}MESHTASTIC_FIRMWARE_ROOT envMESHTASTIC_MCP_TCP_HOST envMESHTASTIC_MCP_TOOLSETS envMESHTASTIC_MCP_READ_ONLY envMESHTASTIC_MCP_CONFIRM envMESHTASTIC_MCP_DATA_DIR envMESHTASTIC_UI_CAMERA_DEVICE envMESHTASTIC_UHUBCTL_LOCATION_TESTER envMESHTASTIC_PIO_BIN envMESHTASTIC_ANDROID_ROOT envMESHTASTIC_APPLE_ROOT envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account meshtastic, which owns the repo
Code last changed 2 days ago
Uses GPL-3.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/meshtastic-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.4.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Meshtastic MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | GPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A home for AI tooling to discover, drive, observe, and test Meshtastic devices and the apps that talk to them. An MCP server plus a bundled agent skill set for closed-loop device ↔ app end-to-end testing.
Extracted and decoupled from the Meshtastic firmware repo's
mcp-server/so it can be
installed and distributed on its own. The firmware-build tools become an optional
capability that lights up only when a firmware checkout is present.
Plug in a Meshtastic device, then:
uvx meshtastic-mcp doctor # check what's available
Inside Claude Code (or any MCP client registered with meshtastic):
list_devices() → find your device port
device_info(port="/dev/cu.usbmodem101") → firmware, region, node count list_nodes(port="/dev/cu.usbmodem101") → mesh peers set_debug_log_api(port="/dev/cu.usbmodem101", enabled=True) send_text(port="/dev/cu.usbmodem101", text="hello mesh", wait_for_tx=True) → tx_confirmed
A node never sees its own transmission on the receive path, so packets_window cannot confirm a local send; wait_for_tx=True reads the firmware's TX log line instead.
No firmware checkout required. Core tools work against any serial or TCP device.
# Install the CLI + MCP server (uv recommended; also works with pipx)
uv tool install 'meshtastic-mcp[ui]' # includes camera/OCR support
uv tool install meshtastic-mcp
uv tool install 'meshtastic-mcp[ui] @ git+https://github.com/meshtastic/meshtastic-mcp'
uv tool install --editable '/path/to/meshtastic-mcp[ui]'
meshtastic-mcp install # claude-code user scope; --client cursor|windsurf|claude-desktop meshtastic-mcp install --local # register the current interpreter (editable/dev install) meshtastic-mcp install --print # just emit the JSON snippet (edit nothing) meshtastic-mcp uninstall # remove the registration (--purge-skills to drop skills too)
claude mcp add meshtastic -s user -- meshtastic-mcp # register with Claude Code meshtastic-mcp skills install # → ~/.agents/skills/ (device-ops, e2e, org-knowledge) meshtastic-mcp skills uninstall # remove them
install edits the client's mcpServers JSON in place (preserving other entries) — it picks the right config path per --client (claude-code / claude-desktop / cursor / windsurf) and --scope (user / project), or pass --config PATH. Add capability env vars with --env KEY=VALUE. Restart the MCP client to pick up the change.
uv tool upgrade meshtastic-mcp # PyPI install: latest release
uv tool install 'meshtastic-mcp[ui] @ git+https://github.com/meshtastic/meshtastic-mcp' # git install: re-run to take master's head git -C /path/to/meshtastic-mcp pull # editable install: re-run its install when dependencies change
The MCP client keeps running the old server until you restart it.
Set env vars pointing at local checkouts to activate firmware-build, Android, and Apple capabilities. The provision subcommand clones everything automatically:
meshtastic-mcp provision # clones firmware + android + apple, prints export commands
source ~/.local/share/meshtastic-mcp/repos/.env
export MESHTASTIC_FIRMWARE_ROOT=~/meshtastic/firmware export MESHTASTIC_ANDROID_ROOT=~/meshtastic/android export MESHTASTIC_APPLE_ROOT=~/meshtastic/apple
esptool — if PlatformIO is installed, esptool is auto-discovered from the
PlatformIO penv and wrapped automatically. No manual setup required.
meshtastic-mcp doctor # verify what's active after setup
A portable core always works against any connected device (serial or tcp://host:port) with no firmware checkout. Optional capabilities activate when their prerequisite is present:
| Capability | Prerequisite | Adds |
|---|---|---|
| core | none | discovery, serial+TCP transport, device_info/list_nodes/admin/send_text/reboot, recorder + log/telemetry/packet/event queries, replay (simulated TCP device + synthetic mesh + fuzzer), input-events, uhubctl, esptool/nrfutil/picotool, the nRF52 bootloader's UF2 drive (nrf52_*) |
| firmware | MESHTASTIC_FIRMWARE_ROOT + PlatformIO pio | build / clean / flash / OTA / board enum / userPrefs |
| android | android CLI + adb | Android-emulator + native-node orchestration for hardware-free e2e |
| apple | xcrun (+ idb for UI) | iOS Simulator / macOS-app orchestration for hardware-free e2e (ios_*); screenshot_set_* registers with this or android and captures matching Android and iOS screens, see docs/screenshot-set.md |
| local-model | a reachable Ollama or OpenAI-compatible llama-server (or a llama binary to start one) | offload tools that push token-heavy work onto a local GPU: summarize/triage recorder windows, e2e-failure first pass, and an offline vision oracle; see docs/local-models.md |
| sdr | [sdr] extra (bundles pyrtlsdrlib, a prebuilt librtlsdr) + an RTL-SDR dongle | RF-compliance oracle: rf_scan occupancy checks and rf_confirm_tx on-air verification, no second radio needed; see docs/rf-oracle.md. *macOS/Homebrew note:* a system librtlsdr from Homebrew is the osmocom fork and lacks rtlsdr_set_dithering, so import rtlsdr fails; the bundled pyrtlsdrlib avoids this and is preferred by pyrtlsdr's loader. |
| tak | the meshtastic-tak SDK, which is not on PyPI: install it with the command doctor prints, or uv sync --group tak in a checkout | real TAKPacketV2 zstd wire compression for the replay sim's TAK squad (profile tak.wire="v2") and its CoT stream to ATAK |
| sdk-cli *(experimental)* | Kotlin SDK headless CLI | alternate device-IO backend over the JVM CLI; see docs/sdk-cli-bridge.md |
| discord | a read-only bot token ($DISCORD_BOT_TOKEN or /meshtastic-mcp/discord.token; doctor prints the path) | read the Meshtastic Discord server: server-side search, history, threads/forum posts, pins, mentions of you, with a per-message role-derived trust tier (discord_*); stdlib only, never posts; see docs/discord.md |
| ble-sniffer | an nRF Sniffer for Bluetooth LE dongle (Nordic VID 0x1915/PID 0x522A) + Nordic's nrfutil-ble-sniffer plugin | capture the phone-to-node BLE link from outside both ends (ble_sniff_start/_poll/_stop), the independent oracle for when the app says "no devices found" and the node says "advertising". ble_sniff_status is core. Receive-only; output is untrusted (a BLE name is arbitrary text from any radio in range); see docs/ble-sniffer.md |
| mvgrind | the mvgrind binary + an OpenCL driver | grind a vanity NodeNum or app color on the GPU (vanity_grind_start/_poll/_stop): a node's number is crc32(x25519_public_key) and the apps paint it with the low 24 bits, so a chosen id or color means searching the keyspace. vanity_preview and vanity_apply are core, so a key ground elsewhere still applies here; see docs/vanity.md |
The active set is logged at startup (meshtastic-mcp capabilities active: …).
Beyond tools, the server exposes MCP resources (meshtastic://doctor, meshtastic://capabilities, and the templated meshtastic://e2e/{loop} for bundled e2e recipes) and prompts (triage_e2e_failure, bringup_device, inbound_loop). The android_docs_search/ android_docs_fetch tools answer Android/Compose questions grounded in the official Knowledge Base.
Tools with a result type in schemas.py advertise it as an output schema. A device, flash or hardware tool that fails returns a tool error (isError) carrying the cause and the tail of any command output.
Build tools (build_meshtasticd.sh, build_android_apk.sh, build_apple.sh) work in two modes:
Dev with existing checkouts — point env vars at your local trees:
export MESHTASTIC_FIRMWARE_ROOT=~/firmware
export MESHTASTIC_ANDROID_ROOT=~/Meshtastic-Android export MESHTASTIC_APPLE_ROOT=~/Meshtastic-Apple
Portable / fresh environment — clone everything in one shot:
meshtastic-mcp provision # clones all three repos, writes a .env file
source ~/.local/share/meshtastic-mcp/repos/.env
provision respects any env vars already set (skips those repos) and writes a sourceable .env for the ones it clones. Run doctor afterwards to confirm all binary deps are present too.
doctor — probe the environmentRun before starting e2e work (also exposed as the doctor MCP tool, so an agent can self-provision):
meshtastic-mcp doctor # per-dependency status + exact, platform-aware install commands
meshtastic-mcp doctor --json # machine-readable; fix_commands[] is ready to run
Probes binaries (pio, adb, xcrun, idb_companion, fb-idb, ffmpeg, uhubctl, OCR) and source repo roots (MESHTASTIC_FIRMWARE_ROOT, MESHTASTIC_ANDROID_ROOT, MESHTASTIC_APPLE_ROOT), reporting ok/missing/degraded with the exact command to fix each — including non-obvious ones (e.g. idb_companion lives in the facebook/fb tap, fb-idb requires Python ≤ 3.12).
| Script | Builds | Key flags | |
|---|---|---|---|
scripts/build_meshtasticd.sh | Native meshtasticd daemon | `--env native\ | native-macos, --ref, --firmware-dir / MESHTASTIC_FIRMWARE_ROOT` |
scripts/build_android_apk.sh | Meshtastic-Android APK | --ref, --variant, --source-dir / MESHTASTIC_ANDROID_ROOT | |
scripts/build_apple.sh | Meshtastic iOS-Simulator .app | --ref, --sim, --source-dir / MESHTASTIC_APPLE_ROOT |
All scripts clone fresh if no source dir is provided, accept --ref to pin a git sha/tag/branch, and print a machine-readable -sha= line for CI provenance.
Tools that reboot, erase, reflash or rewrite a board take confirm. Without it, a client that supports elicitation asks the human (Allow: ?), and a client that cannot ask gets a refusal naming confirm=True. MESHTASTIC_MCP_CONFIRM=human makes the irreversible ones (factory_reset, erase_and_flash, nrf52_factory_erase, vanity_apply, the destructive vendor calls) ask even when the agent passes confirm=True. See docs/confirmations.md.