---
title: "nephmesh"
description: "Report-only Meshtastic intent planning, spectrum reduction, and the MeshToad plus T-Deck bench. Does not write to a radio unless a skill says so and a human runs it."
canonical: https://agentpluginsdirectory.com/plugins/nephmesh
last-updated: 2026-09-27
---

# nephmesh
Report-only Meshtastic intent planning, spectrum reduction, and the MeshToad plus T-Deck bench. Does not write to a radio unless a skill says so and a human runs it.
- Slug: nephmesh
- Publisher: blisspixel
- Repository: https://github.com/blisspixel/NephMesh
- Manifest: agent-plugin/plugin.json
- Version: 0.2.1
- License: Apache-2.0
- Category (editorial): integrations
- Skills: 3 (meshtoad-bench, operator-demo, plan-intent)
- MCP servers: 1 (nephmesh)
- Stars: 1
- Repository created: 2026-08-04
- Repository last pushed: 2026-08-26
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/nephmesh
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What nephmesh does, in the publisher's words

An Agent Plugins 1.0.0 package around the binaries this repo already ships. It is a directory layout plus manifests, not a new control loop.

mcp.json launches nephmesh-mcp from PATH (stdio). Build it from operators/meshtastic-operator/cmd/nephmesh-mcp. The tools stay report-only: plan_intent and sense_spectrum do not write to a radio.

Point a compatible client at this directory. Client-specific install, trust, and UX stay with the client. The agent is never the live reconcile loop (ADR 0002).

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/blisspixel/NephMesh/HEAD/agent-plugin/README.md

## Skills

- meshtoad-bench: Run or interpret the MeshToad plus handheld LoRa bench. Use when the user has a CH341 meshtasticd gateway on a Linux USB host and a USB handheld, or asks about the two-radio RF proof.
- operator-demo: Run the hardware-free MeshtasticNode operator demo against meshtasticd --sim. Use when the user wants to see reconcile without radios or a cluster.
- plan-intent: Dry-run a CommunicationIntent through NephMesh's report-only compiler. Use when the user wants to know if a mesh design is feasible or within the airtime budget, with no cluster and no radio write.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- nephmesh: transport: stdio; command: nephmesh-mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.