meshtastic-mcp — Claude Code MCP server: what it does, how to install
The meshtastic-mcp MCP server for Claude Code discovers, drives, and tests Meshtastic hardware over serial and TCP connections.
GPL-3.0 ★ 23 updated 2026-11-17
claude mcp add --env MESHTASTIC_FIRMWARE_ROOT=<MESHTASTIC_FIRMWARE_ROOT> --env MESHTASTIC_MCP_TCP_HOST=<MESHTASTIC_MCP_TCP_HOST> --env MESHTASTIC_MCP_TOOLSETS=<MESHTASTIC_MCP_TOOLSETS> --env MESHTASTIC_MCP_READ_ONLY=<MESHTASTIC_MCP_READ_ONLY> --env MESHTASTIC_MCP_CONFIRM=<MESHTASTIC_MCP_CONFIRM> --transport stdio meshtastic-mcp -- uvx meshtastic-mcpWhat meshtastic-mcp does
The server bridges AI assistants with Meshtastic devices for automated end-to-end testing and hardware diagnostics. Its core features work immediately against any connected device without requiring a firmware repository checkout.
The tool is distributed via PyPI and runs through uvx. Optional capabilities like firmware compilation or Android orchestration activate when local checkouts and environment variables such as MESHTASTIC_FIRMWARE_ROOT are configured.
What it helps with
- discover connected Meshtastic device ports and nodes
- query device firmware version, region, and node count
- send text messages across the mesh network
- verify RF compliance using an RTL-SDR dongle
Example prompts for the agent
- List connected Meshtastic devices
- Get device info for port /dev/cu.usbmodem101
- Send a text message to the mesh network
How to install meshtastic-mcp
Platform CLI
claude mcp add --env MESHTASTIC_FIRMWARE_ROOT=<MESHTASTIC_FIRMWARE_ROOT> --env MESHTASTIC_MCP_TCP_HOST=<MESHTASTIC_MCP_TCP_HOST> --env MESHTASTIC_MCP_TOOLSETS=<MESHTASTIC_MCP_TOOLSETS> --env MESHTASTIC_MCP_READ_ONLY=<MESHTASTIC_MCP_READ_ONLY> --env MESHTASTIC_MCP_CONFIRM=<MESHTASTIC_MCP_CONFIRM> --transport stdio meshtastic-mcp -- uvx meshtastic-mcpReplace <…> with your own values. 6 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from meshtastic-mcp <command>
Platform CLI
codex mcp add meshtastic-mcp --env MESHTASTIC_FIRMWARE_ROOT=<MESHTASTIC_FIRMWARE_ROOT> --env MESHTASTIC_MCP_TCP_HOST=<MESHTASTIC_MCP_TCP_HOST> --env MESHTASTIC_MCP_TOOLSETS=<MESHTASTIC_MCP_TOOLSETS> --env MESHTASTIC_MCP_READ_ONLY=<MESHTASTIC_MCP_READ_ONLY> --env MESHTASTIC_MCP_CONFIRM=<MESHTASTIC_MCP_CONFIRM> -- uvx meshtastic-mcpReplace <…> with your own values. 6 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from meshtastic-mcp <command>
Config file
{
"mcpServers": {
"meshtastic-mcp": {
"command": "uvx",
"args": [
"meshtastic-mcp"
],
"env": {
"MESHTASTIC_FIRMWARE_ROOT": "<MESHTASTIC_FIRMWARE_ROOT>",
"MESHTASTIC_MCP_TCP_HOST": "<MESHTASTIC_MCP_TCP_HOST>",
"MESHTASTIC_MCP_TOOLSETS": "<MESHTASTIC_MCP_TOOLSETS>",
"MESHTASTIC_MCP_READ_ONLY": "<MESHTASTIC_MCP_READ_ONLY>",
"MESHTASTIC_MCP_CONFIRM": "<MESHTASTIC_MCP_CONFIRM>"
}
}
}
}Replace <…> with your own values. 6 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from meshtastic-mcp <command>
Config file
{
"servers": {
"meshtastic-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"meshtastic-mcp"
],
"env": {
"MESHTASTIC_FIRMWARE_ROOT": "<MESHTASTIC_FIRMWARE_ROOT>",
"MESHTASTIC_MCP_TCP_HOST": "<MESHTASTIC_MCP_TCP_HOST>",
"MESHTASTIC_MCP_TOOLSETS": "<MESHTASTIC_MCP_TOOLSETS>",
"MESHTASTIC_MCP_READ_ONLY": "<MESHTASTIC_MCP_READ_ONLY>",
"MESHTASTIC_MCP_CONFIRM": "<MESHTASTIC_MCP_CONFIRM>"
}
}
}
}Replace <…> with your own values. 6 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from meshtastic-mcp <command>
Platform CLI
gemini mcp add -e MESHTASTIC_FIRMWARE_ROOT=<MESHTASTIC_FIRMWARE_ROOT> -e MESHTASTIC_MCP_TCP_HOST=<MESHTASTIC_MCP_TCP_HOST> -e MESHTASTIC_MCP_TOOLSETS=<MESHTASTIC_MCP_TOOLSETS> -e MESHTASTIC_MCP_READ_ONLY=<MESHTASTIC_MCP_READ_ONLY> -e MESHTASTIC_MCP_CONFIRM=<MESHTASTIC_MCP_CONFIRM> meshtastic-mcp uvx meshtastic-mcpReplace <…> with your own values. 6 more environment variables are in the server README. uvx runs the command named after the package; if the README names another one, use uvx --from meshtastic-mcp <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about meshtastic-mcp
How to install meshtastic-mcp in Claude Code?
Run claude mcp add meshtastic-mcp -- uvx meshtastic-mcp to register the MCP server.
What does meshtastic-mcp do?
It exposes tools for AI agents to interact with Meshtastic hardware, read telemetry logs, manage firmware, and test companion apps.
What is needed to run meshtastic-mcp?
You need uvx or uv installed along with a physical or simulated Meshtastic device accessible via serial port or TCP.