Mesh Bot

Mesh Bot is a command bot that connects to a MeshCore companion radio over a USB serial connection and answers commands sent in private channels.

  • AI
  • Network Services
  • Other
  • Productivity
  • Tools & Utilities
Mesh Bot is a command bot that connects to a MeshCore companion radio over a USB serial connection and answers commands sent in private channels. It can also periodically fetch and log repeater status data, such as uptime, transmit air time, signal-to-noise ratio, and noise floor, to a CSV file at a configurable interval, making it a useful tool for testing MeshCore repeater setups and communication range.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

68/100 Good

Maintained
95last commit 12 days ago
Popular
3135 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
701 GB minimum RAM
Security check
90no serious findings, CI

Availability: platform listings confirmed today, links checked 20 days ago

GitHub stars
35
Open issues
4
Last commit
2026-11-09
License
Apache-2.0
Activity
declining

Checked 6 days ago - source: GitHub (Cyclenerd/meshcore-bot)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 1 CPU core(s).

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add your Mesh API token before starting Create a Mesh API token and keep it private. Put it in your Python client or set MESH_API_KEY (the place your Node code looks for the key); without it, Mesh says you are not authorized and your embedding calls fail. source
  • Install the Mesh CLI if you will use it Run pipx install meshapi-code; pipx is a helper that puts command-line programs on your computer. Without it, the Mesh CLI commands will not be available in your terminal. source
  • Use the pip backend if CLI install fails If pipx says it cannot find uv, run pipx install meshapi-code --backend pip. That fallback lets the CLI install finish without the missing uv piece blocking it. source
  • Installation Node.js must be installed before running the bot. source
  • Usage The bot only responds to commands in private channels to prevent spam in public channels. source
  • Runtime Requirement The bot runs on Node.js; install the Node.js runtime before starting it. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can Mesh-Bot be self-hosted with Docker?

Yes, the project page presents a Docker install guide for self-hosting Mesh-Bot.

What radio connection options does Mesh-Bot support?

It can connect to one or more radios over TCP, serial, BLE, MeshCore, or MQTT.

Does Mesh-Bot respond to all traffic it hears?

No, it listens for traffic directed at it.

How are Mesh-Bot replies generated?

It replies through a cascading chain of local and API language models.

Answers sourced from github.com, selfhost.directory

Community

Collected 44 days ago - public community threads