Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.meshtastic/meshtastic-mcp

PYPI · MESHTASTIC-MCP

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

Available components

69 Trust /100

Last scanned (13 hours ago)

Scores higher than 62% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 64 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to meshtastic/meshtastic-mcp). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-only).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 13412 tokens (~174/item across 77 items; 73 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 74 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.96 functional
  • 18 Nov 26 +3
    • Known CVEs: pass → partial ▼ security
    • Tool coverage: 0% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: good → excellent functional
    • Dependency health: 0.96 → partial functional
    • Package version: 0.3.0 → 0.4.0 functional
  • 17 Nov 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/meshtastic-mcp@0.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo meshtastic/meshtastic-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/meshtastic/meshtastic-mcp/.github/workflows/release.yml@refs/tags/v0.4.0
Rekor log index 3957659290
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:f1b1001a4dc88a710630a6b3056b08688699b47a4f113acf365e9301cff4939b

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 64 packages
Packages resolved 64
Stale 3
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 73 exposed · ~13,304 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
replay_inject_waypoint ~312

Inject a WAYPOINT_APP packet (portnum 8), geofence included, into a replay session. Set `geofence_radius`, `bbox` or both, then move a node across the boundary with `replay_inject(sid, "position", {"lat": ..., "lon": ...}, from_node=<tracker>)`. See docs/replay.md. Returns `{id, queued, connected}`, or `{error}` for an unknown session.

NameTypeReqDescription
bbox––Geofence box `[south, west, north, east]` in decimal degrees.
channelstring–Channel name to send on.
countinteger–How many copies to send.
descriptionstring–Waypoint description.
from_node––Sender node number; omit for a synthetic injector node.
geofence_radiusinteger–Geofence circle radius in meters; 0 for none.
iconinteger–Icon as a Unicode code point; 0 sets none.
latnumberyesWaypoint latitude in decimal degrees.
lonnumberyesWaypoint longitude in decimal degrees.
namestring–Waypoint name.
notify_favorites_onlyboolean–Notify only for favorite nodes.
notify_on_enterboolean–Notify when a node enters the geofence.
notify_on_exitboolean–Notify when a node leaves the geofence.
session_idstringyesSession id from `replay_start`.

Structured output declared, but exposes no named fields.

No examples provided.

replay_start ~970

Start a simulated Meshtastic TCP device that streams a capture to an app. An app, an AVD at `10.0.2.2:<port>`, or the Python library connects to `host:port` and gets a paced packet stream restamped to now. Poll `replay_status`, stop with `replay_stop`. Pacing, highest first: `duration`, then `rate`, then `speed`. Give concurrent sessions distinct `observer_num`s. Every parameter and example: docs/replay.md. Returns the session status, as `replay_status` reports it: `{id, capture, listen, connect, mode, packets_total, packets_sent, connected, ...}`.

NameTypeReqDescription
announce_intervalnumber–Seconds between "Replay Clock" progress posts to the busiest channel; 0 is off.
beacon_listenboolean–Advertise the mesh beacon module as listening, so the app keeps `MESH_BEACON_APP` packets.
channels––Channel list that splits a SQLite capture by OTA hash with real PSKs, each `{"name", "psk", "primary", "ota_hashes", "catch_all"}`.
clock_anchor––Epoch seconds the window's last packet is stamped as, so sessions sharing it show identical times; omit to stamp each packet now.
dupe_everyinteger–Simulate a duplicate radio receive every Nth packet; 0 is off.
duration––Play the whole window in N wall-clock seconds; wins over `rate`.
end––Window end, ISO-8601.
firmware_editionstring–The app's event banner, such as `VANILLA`, `DEFCON`, `BURNING_MAN` or `HAMVENTION`.
firmware_version––Reported firmware build; omit for the edition's default.
fuzz––Makes the stream hostile: a preset (`light`, `parser`, `adversary`, `chaos`) or a dict of overrides with an optional `preset` base.
fuzz_seedinteger–Fuzz seed, so a crash reproduces.
holdboolean–Play the window once per connection, then stay connected and quiet; ignored with `loop`.
hoststring–Listen address; `0.0.0.0` serves every interface.
kindstring–`auto` infers it from `source`; or `sim`, `sqlite`, `jsonl`.
limit_nodesinteger–Cap on a file source's node DB.
local_metrics_intervalnumber–Seconds between the connected node's `DEVICE_METRICS` packets; 0 is off.
loopboolean–Repeat the window when it ends.
max_gapnumber–Cap on idle seconds between packets.
mdns––Advertise the session over mDNS as `_meshtastic._tcp`; omit for on unless bound to loopback only.
modem_presetstring–Advertised LoRa preset, such as `LONG_FAST`.
node_delaynumber–Seconds between NodeInfos during the node DB download.
observer_lat––Connected node's latitude in 1e-7 degrees; omit for the capture's median position.
observer_lon––Connected node's longitude in 1e-7 degrees; omit for the capture's median position.
observer_num––This session's node number; omit for the process default (`MESHTASTIC_REPLAY_OBSERVER_NUM`).
portinteger–TCP port the session listens on for the app.
rate––Steady packets per second, ignoring capture timing; wins over `speed`.
sim_daysinteger–Days of traffic a generated mesh spans, ending now unless `start` is set.
sim_nodesinteger–Node count of a generated mesh.
sim_profile––Overrides deep-merged over a generated preset, as a dict or JSON object, never a file path.
sim_seedinteger–Seed for a generated mesh.
sourcestring–`meshcon`/`sim`, `burningman`, `defcon`, `conference-stress` (generated meshes), a `*.db`/`*.db.gz` SQLite capture or a recorder `*.jsonl`.
speednumber–Multiplier on the capture's own cadence.
start––Window start, ISO-8601 (UTC when no zone is given).
stats_intervalnumber–Seconds between the connected node's LocalStats updates; 0 keeps only the initial snapshot.

Structured output declared, but exposes no named fields.

No examples provided.

replay_status ~102

Status of replay sessions: connection state, packets sent and total, mode. Returns one session's `{id, capture, listen, connect, mode, target_rate, achieved_rate, packets_total, packets_sent, injected, connected, client, ended, error, fuzz, mdns, ...}`, `{sessions: [...]}` for all, or `{error}` for an unknown id.

NameTypeReqDescription
session_id––One session's id; omit for every running session.

Structured output declared, but exposes no named fields.

No examples provided.

replay_stop ~48

Stop a replay session, or every session when `session_id` is omitted. Returns `{stopped}`, the ids it stopped.

NameTypeReqDescription
session_id––Session to stop; omit to stop all.

Structured output declared, but exposes no named fields.

No examples provided.

send_input_event ~215

Inject an InputBroker event (button / key / gesture) into the device UI. Drives the same code path as a physical button press. Returns `{ok, event_code, kb_char}`.

NameTypeReqDescription
event_code–yesA numeric event code (0..255) or a name like `"RIGHT"`, `"SELECT"`, `"FN_F1"`. Common codes: SELECT=10, UP=17, DOWN=18, LEFT=19, RIGHT=20, CANCEL=24, BACK=27, FN_F1..F5=241..245.
kb_charinteger–A character code (0..255) to type with the event.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
touch_xinteger–Touch x coordinate (0..65535), for a tap such as `USER_PRESS`.
touch_yinteger–Touch y coordinate (0..65535).
NameTypeReqDescription
event_codeintegeryesthe numeric code a name resolved to
kb_charintegeryes–
okbooleanyes–

No examples provided.

send_text ~348

Send a text message over the mesh. Delivery is async and best effort: by default this returns once the packet is queued. `wait_for_tx=True` also polls for the firmware's `Started Tx (id=...)` log line or a neighbor's rebroadcast. `tx_confirmed` is true (seen), false (logs flowed, no TX) or null (not observable, usually because firmware logs are not captured, which does NOT mean failure); call `set_debug_log_api(True)` on the port first to make it meaningful. `tx_unconfirmed_reason` says which case. `packets_window` cannot confirm a local send. Returns `{ok, packet_id, destination}`, plus `{tx_confirmed, tx_latency_s, tx_unconfirmed_reason?}` with `wait_for_tx=True`.

NameTypeReqDescription
channel_indexinteger–The channel to send on.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
textstringyesThe message.
to––A node id ("!abcdef01") or number to direct-message; omit to broadcast ("^all").
tx_linger_snumber–Seconds to hold the connection open after the send, so the firmware's ~4 s politeness delay and the airtime finish before the port resets, which would drop a queued broadcast.
tx_timeout_snumber–Seconds `wait_for_tx` polls before giving up.
wait_for_txboolean–Also wait for evidence that the packet reached the air.
want_ackboolean–Ask the recipient for an acknowledgement.
NameTypeReqDescription
destination–yes`^all` for a broadcast
okbooleanyes–
packet_id–yes–
tx_confirmed––true: TX seen; false: logs flowed and showed no TX; null: not observable, usually because firmware logs are not captured, which is not a failure
tx_latency_s–––
tx_unconfirmed_reasonstring–why `tx_confirmed` is false or null

No examples provided.

serial_close ~55

Terminate a serial monitor session and free its port. Returns `{ok: true}` on success, or `{ok: false, reason}` if the session is unknown.

NameTypeReqDescription
session_idstringyesId from `serial_open`.
NameTypeReqDescription
okbooleanyesfalse when `session_id` is unknown
reasonstring––

No examples provided.

serial_list ~15

List all active serial monitor sessions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

serial_open ~200

Open a `pio device monitor` session reading from `port`. Needs PlatformIO and `MESHTASTIC_FIRMWARE_ROOT`. The session holds the port until `serial_close`, so the admin tools cannot use it meanwhile. Returns `{session_id, resolved_baud, resolved_filters, env}`: the `session_id` for `serial_read` / `serial_close`, plus the baud and filters pio resolved.

NameTypeReqDescription
baudinteger–Line speed, used without `env`.
env––A PlatformIO env whose `monitor_speed` and `monitor_filters` pio takes from platformio.ini, which turns on the ESP32 exception decoders for firmware debugging.
filters––Monitor filters, used without `env`: default ["direct"]; others are time, hexlify, esp32_exception_decoder, esp32_c3_exception_decoder, log2file.
portstringyesThe serial port to read.

Structured output declared, but exposes no named fields.

No examples provided.

serial_read ~143

Read buffered lines from a serial monitor session. Returns `{lines, new_cursor, eof, dropped}`. `dropped` counts lines that aged out of the 10k-line ring buffer between reads, so a value > 0 means you missed data.

NameTypeReqDescription
max_linesinteger–Cap on the lines returned.
session_idstringyesId from `serial_open`.
since_cursor––Omit to get everything since your last `serial_read` (an advancing cursor). Pass `since_cursor=N` to re-read from a specific point, or `since_cursor=0` to read from the start of the in-memory buffer.

Structured output declared, but exposes no named fields.

No examples provided.

set_channel_url ~108

Import channels from a Meshtastic channel URL. Replaces the device's channel set with the channels encoded in `url`. Idempotent: applying the same URL twice leaves identical channel state. Returns `{ok, channels_imported}`.

NameTypeReqDescription
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
urlstringyesA Meshtastic channel URL, such as `get_channel_url` returns.
NameTypeReqDescription
channels_importedintegeryeschannels not DISABLED after the import
okbooleanyes–

No examples provided.

set_config ~180

Set one config field via dot-path and write it to the device. Idempotent: calling with the same path+value twice leaves identical state. Call `reboot()` afterwards to commit the change to NVS. Returns `{ok, path, section, parent, old_value, new_value}`.

NameTypeReqDescription
pathstringyesDot-path of one scalar field, such as "lora.region", "lora.modem_preset", "device.role", "mqtt.enabled" or "mqtt.address".
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
value–yesThe new value, such as "US", "LONG_FAST", "ROUTER", True or "host". Enum fields accept their name (case-insensitive) or int.
NameTypeReqDescription
new_value–yesenum fields by name
okbooleanyes–
old_value–yesenum fields by name
parentstringyes`localConfig` or `moduleConfig`
pathstringyes–
sectionstringyes–

No examples provided.

set_debug_log_api ~162

Toggle `security.debug_log_api_enabled` on the local node. When on, firmware streams its log lines as `LogRecord` protobufs over the StreamAPI, so the recorder captures them through the same connection the admin tools use, with no `pio device monitor` session and no port-lock conflict. `send_text(wait_for_tx=True)` needs it. Persists across reboot (NVS); `factory_reset` wipes it. Safe to leave on under traffic. Returns `{ok, debug_log_api_enabled}`.

NameTypeReqDescription
enabledbooleanyesTrue turns the log stream on, False turns it off.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.

Structured output declared, but exposes no named fields.

No examples provided.

set_owner ~95

Set the device's owner long name and optional short name. Returns `{ok, long_name, short_name}`.

NameTypeReqDescription
long_namestringyesThe owner's long name.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
short_name––The owner's short name, at most 4 characters; omit to keep the current one.
NameTypeReqDescription
long_namestringyes–
okbooleanyes–
short_name–yesnull when the call passed none

No examples provided.

shutdown ~109

Shut down the connected node in `seconds` seconds. Requires confirm=True, or the user's answer when the client can ask. Returns `{ok, shutting_down_in_s}`.

NameTypeReqDescription
confirmboolean–`True` once the user agreed; omitted, a client that can ask prompts the human.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
secondsinteger–Delay before the node shuts down.
NameTypeReqDescription
okbooleanyes–
shutting_down_in_sintegeryes–

No examples provided.

telemetry_timeline ~211

Time series of one telemetry field, bucket-mean downsampled to <= max_points. Returns `{points: [{ts, value}], samples, min, max, slope_per_min, window}`. `slope_per_min` is a linear regression in units/minute: a negative slope on free_heap over a long window means a real leak. The `local` (LocalStats) cadence is the device's `device_update_interval`, about 60 s, so 1 h gives about 60 raw points.

NameTypeReqDescription
fieldstring–The field in snake_case or camelCase; common aliases (free_heap, heap_free_bytes) are normalized.
max_pointsinteger–Cap on the points returned.
port––Only telemetry from this port.
variantstring–One of device, local, environment, power, airQuality, health, host.
windowstring–How far back to look, such as "1h" or "-30m".

Structured output declared, but exposes no named fields.

No examples provided.

touch_1200bps ~184

Open `port` at 1200 baud and close it, rebooting an nRF52840, native-USB ESP32-S3, RP2040 or similar into its USB bootloader; on an nRF52 it also drops DTR, which its Adafruit core needs. Then reports the bootloader's port: a new one, or the same node under a new PID (Linux keeps the /dev/ttyACM node and renames the /dev/serial/by-id link). Erases nothing; it is annotated destructive because it reboots the device. Returns `{ok, former_port, new_port, new_port_vid_pid, ...}`.

NameTypeReqDescription
portstringyesThe board's serial port.
settle_msinteger–Milliseconds to hold the port open at 1200 baud before closing it.

Structured output declared, but exposes no named fields.

No examples provided.

triage_bundle ~153

Collect the device-plane artifacts for an e2e-failure window in one call. Returns `{window, packets, logs, events}` from the recorder. Pairs with the `triage_e2e_failure` prompt and the `triage.md` skill reference: align these timestamps with the app `layout`/`screen capture` at the deadline to classify a failure (never-sent / sent-not-received / received-not-rendered / rendered-not-asserted).

NameTypeReqDescription
endstring–Window end, in the same forms.
startstring–Window start: `-5m`, `now` or ISO 8601; the default is the last 2 minutes.

Structured output declared, but exposes no named fields.

No examples provided.

uhubctl_cycle ~226

Power a USB hub port off, wait `delay_s` seconds, then on. The hard reset for a board whose USB serial has wedged (calls to it fail with "Power-cycle it (uhubctl_cycle)"). One call instead of off+on, with the timing handled in-process. Target by (location, port) from `uhubctl_list`, or by role (see `uhubctl_power`). Requires `confirm=True`, or the user's answer when the client can ask. Returns `{action, location, port, delay_s, duration_s, ...}`.

NameTypeReqDescription
confirmboolean–`True` once the user agreed; omitted, a client that can ask prompts the human.
delay_sinteger–Seconds the port stays off, 0..60.
location––The hub location from `uhubctl_list`.
port––The port number on that hub.
role––A device role, resolved as in `uhubctl_power`; not with `location`/`port`.

Structured output declared, but exposes no named fields.

No examples provided.

uhubctl_list ~159

List every USB hub + per-port device attachment as seen by `uhubctl`. Read-only. Each hub has its location, descriptor, whether it supports per-port power switching, and its populated ports with the attached VID:PID; check it before a power-cycle. `location` is uhubctl notation (`1-1.3`) on Linux and macOS. On Windows the backend is VirtualHere's `vhfilter` (uhubctl cannot switch port power there) and a location is the hub's PnP device path, e.g. `USB\VID_0BDA&PID_0411\6&28cf390b&0&2`. Pass either form to the power tools unchanged.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

uhubctl_power ~284

Power a USB hub port on or off (`uhubctl -a on|off`, or `vhfilter --switch-port` on Windows). Target the port by either (`location`, `port`), e.g. `location="1-1.3", port=2` as `uhubctl_list` reports it, OR by `role`, never both. `action="off"` requires `confirm=True`, or the user's answer when the client can ask: the attached device disappears from the OS at once. `on` never asks. Returns `{action, location, port, delay_s, duration_s, ...}`.

NameTypeReqDescription
actionstringyes`on` or `off`.
confirmboolean–`True` once the user agreed; omitted, a client that can ask prompts the human. Only `off` asks.
location––The hub location from `uhubctl_list`: uhubctl notation, or a PnP device path on Windows.
port––The port number on that hub.
role––A device role ("nrf52", "esp32s3"). Role lookup honors `MESHTASTIC_UHUBCTL_LOCATION_<ROLE>` + `_PORT_<ROLE>` env vars first, then falls back to VID auto-detection.

Structured output declared, but exposes no named fields.

No examples provided.

vanity_apply ~277

Write a vanity private key to a device, moving it to the matching NodeNum. Destructive: it replaces the node's identity. Peers keep the old public key until they see the new NodeInfo, and anything naming the old node (admin keys, DM history) must be re-pointed; keep the old key for a way back. Requires confirm=True, or the user's answer when the client can ask (always, with `MESHTASTIC_MCP_CONFIRM=human`), a clamped key, and `lora.region` set, since firmware will not derive keys while it is UNSET. The board reboots (~7 s). See docs/vanity.md.

NameTypeReqDescription
confirmboolean–`True` once the user agreed; omitted, a client that can ask prompts the human.
port––Serial port or `tcp://host[:port]`; omit to auto-select the one likely Meshtastic device.
private_keystringyesThe vanity private key, hex or base64, as `vanity_grind_poll` or `vanity_preview` shows it.
verifyboolean–Reconnect after the reboot and check the new number.
verify_timeout_snumber–Seconds `verify` waits for the node to come back.

Structured output declared, but exposes no named fields.

No examples provided.

vanity_preview ~96

What node id and color a private key produces. No device, no grinder. Returns the node id, NodeNum, the RGB the apps paint it (and the black/white they put on top), and whether the scalar is clamped. Use it to check a key someone else ground before `vanity_apply` writes it.

NameTypeReqDescription
private_keystringyesThe X25519 private key, hex or base64.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.meshtastic/meshtastic-mcp server?

io.github.meshtastic/meshtastic-mcp runs locally as a PyPI package, launched with uvx meshtastic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · meshtastic-mcp

# add to Claude Code
claude mcp add meshtastic-meshtastic-mcp -- uvx meshtastic-mcp
Common questions

What is the io.github.meshtastic/meshtastic-mcp server?

io.github.meshtastic/meshtastic-mcp is listed in the public MCP registry as io.github.meshtastic/meshtastic-mcp. Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP. This page covers its PyPI package (meshtastic-mcp).

Is the io.github.meshtastic/meshtastic-mcp server safe to use?

io.github.meshtastic/meshtastic-mcp scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.meshtastic/meshtastic-mcp server expose?

io.github.meshtastic/meshtastic-mcp exposes 73 tools: doctor, triage_bundle, list_devices, device_info, list_nodes, and 68 more. Their descriptions and schemas cost roughly 13,304 tokens of context every time the server is loaded.

Is the io.github.meshtastic/meshtastic-mcp server still maintained?

io.github.meshtastic/meshtastic-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.meshtastic/meshtastic-mcp server under?

io.github.meshtastic/meshtastic-mcp declares the GPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.meshtastic/meshtastic-mcp server?

VerifyMCP ran 15 checks on io.github.meshtastic/meshtastic-mcp, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.meshtastic/meshtastic-mcp: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.