Meshtastic Device Ops
Discover, connect to, drive, configure, observe, and flash Meshtastic devices through the Meshtastic MCP server. Use when an agent needs to bring up a radio (serial or TCP), read or change device/channel config, send messages, inspect the node DB, watch live packets/telemetry/logs via the recorder, recover a bricked device, or build/flash firmware. Covers the non-e2e MCP tool surface; for cross-plane device↔app testing use the `meshtastic-e2e` skill.
Install
npx skills add meshtastic/meshtastic-mcp --skill meshtastic-device-opsgit clone --depth 1 https://github.com/meshtastic/meshtastic-mcp.git /tmp/meshtastic-mcp
mkdir -p ~/.claude/skills
cp -r /tmp/meshtastic-mcp/src/meshtastic_mcp/skills/meshtastic-device-ops ~/.claude/skills/meshtastic-device-opsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Meshtastic device operations (via the MCP server) The Meshtastic MCP server exposes a large tool surface, plus resources and prompts. This skill maps common operator intents to the right tools and the safe order to use them. ## First: know your environment - **`doctor`** (tool) or the **`meshtastic://doctor`** resource — what's installed, what's missing, and the exact command to acquire it. Call this first if any tool fails with a missing-prerequisite error, or before an e2e/flash run. - **`meshtastic://capabilities`** resource — one line: which capability groups are active (`core`, `firmware`, `android`, `apple`). - Prereq binaries are gated: `firmware` tools (build/flash/boards/userprefs) register only when `MESHTASTIC_FIRMWARE_ROOT` + `pio` are present. Core (admin/recorder/transport) is always on. - The server's `MESHTASTIC_MCP_TOOLSETS` / `MESHTASTIC_MCP_READ_ONLY` can hide whole groups (the flash and `nrf52_*` tools live in `hardware` and `firmware`). A tool that is not listed cannot be called; ask the user to widen the setting rather than working around it. ## Connect Two transports, same admin surface: - **Serial:** a USB port from `list_devices` (e.g. `/dev/cu.usbmodem101`). - **TCP:** `tcp://host:port` (a networked node, or a virtual `meshtasticd` at `127.0.0.1:4403`). **Prefer the CLI subcommands for read-only discovery** — they cost no MCP schema tokens and work without the server running:
Details
- Skill name
meshtastic-device-ops- Repository
- meshtastic/meshtastic-mcp
- Path
src/meshtastic_mcp/skills/meshtastic-device-ops/SKILL.md- License
- GPL-3.0
- Repo updated
- 18 November 2026
FAQ
What does the Meshtastic Device Ops skill do?
Discover, connect to, drive, configure, observe, and flash Meshtastic devices through the Meshtastic MCP server. Use when an agent needs to bring up a radio (serial or TCP), read or change device/channel config, send messages, inspect the node DB, watch live packets/telemetry/logs via the recorder, recover a bricked device, or build/flash firmware. Covers the non-e2e MCP tool surface; for cross-plane device↔app testing use the `meshtastic-e2e` skill.
How do I install the Meshtastic Device Ops skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add meshtastic/meshtastic-mcp --skill meshtastic-device-ops. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Meshtastic Device Ops popular?
It lives in meshtastic/meshtastic-mcp, which has 23 GitHub stars and 9 forks.
Related skills
Meshtastic E2E
23meshtastic/meshtastic-mcp
Closed-loop end-to-end testing of a Meshtastic device and a Meshtastic app (Android, Apple, or the Compose desktop app) together. Use when validating that an action on the radio (send a text, change config, a node beacon, a power-cycle) surfaces correctly in the app UI, or that an action in the app produces the correct on-air/on-device result. Drives the firmware device via the Meshtastic MCP server and the app via the Android CLI (`android` + `adb`), the Apple toolchain (`xcrun simctl` + `idb`), or the Compose Hot Reload MCP server for desktop, then cross-asserts one plane against the other.
Meshtastic Org Knowledge
23meshtastic/meshtastic-mcp
Find and answer questions across all Meshtastic GitHub repos — what projects exist, what their docs say, their current status (releases, open PRs/issues, recent commits), and how they relate. Use when a question spans more than one repo, or asks "which project does X", "what's the status of Y", "where is Z documented", or "what changed recently across the org".
Macos Test Triage
49robinebers/skills
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
Trellis Delivery Controller Zh
44coldwateryi/trellis-skills
Trellis 需求交付总入口和流程控制器。用于用户希望只调用一个 Trellis skill 自动判断当前阶段,并在需求分析、MVP 任务规划、MVP 后差距审计、交付 loop、TDD 实现、系统调试、双阶段评审和最终验收之间进行路由、推进和安全门控制的场景。适合基于 trellis-zero-to-mvp-zh、trellis-mvp-to-delivery-zh、trellis-implement-tdd-zh、trellis-debug-systematic-zh 和 trellis-review-twostage-zh 形成端到端交付闭环。
Macos Swiftpm
49robinebers/skills
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
Trellis Implement TDD
44coldwateryi/trellis-skills
Implement a Trellis subtask using strict TDD (RED→GREEN→REFACTOR), turning acceptance criteria into code one by one. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—transforms "understand and implement requirements" into a mechanical "make this failing test green" loop with objective signals at every step.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.