MESH-API: an MCP bridge connecting AI agents to LoRa meshes
MESH-API, from Mr Tbot, is an experimental MCP server and router that connects AI assistants to off-grid LoRa radio networks. It translates natural language prompts into mesh actions and routes messages between local radios and internet services, supporting API extensions and GPS emergency alert routing. The project targets IoT hobbyists, Meshtastic users, and developers who need programmatic control of remote mesh nodes without continuous internet connectivity.
It bridges MCP agents to LoRa mesh radios for actionable routing
mesh-api runs as a dedicated Model Context Protocol server and router, giving AI clients programmatic access to Meshtastic and MeshCore networks. Built-in MCP support lets agents send and receive mesh messages and pair those messages with internet endpoints. The extension set links radio traffic to services such as Twilio, Discord, and Home Assistant to move information between radio and online channels.
Agent-generated actions execute on reachable nodes but depend on network state
The tool converts prompts into remote-control actions and GPS emergency notifications that can be dispatched via SMS, email, or Discord, demonstrating practical automation potential. Custom command support performs node control when nodes are reachable, so execution depends on mesh connectivity and hardware availability. Deployments require verification of command mappings to prevent unintended actions on distant nodes.
Using it requires Python hosting and physical LoRa hardware
mesh-api requires a Python environment for hosting and a live connection to Meshtastic or MeshCore nodes, which sets a technical setup requirement. It accepts connections from any MCP client, for example Claude Desktop, and can connect to on-premise model hosts; the project lists integrations with local model providers such as Ollama and LM Studio to keep processing local when configured.
Extension breadth expands workflows but routes some data to external services
The library of more than 30 API extensions broadens how radio-originated messages are consumed, from SMS gateways to home automation. Enabling those integrations sends mesh-originated data to third-party channels, so administrators must decide which routes to activate and validate what information leaves the mesh. The developer publishes the project open-source and niche community feedback recognizes it as a capable experimental bridge.
mesh-api suits technically proficient hobbyists willing to manage hardware and verification
mesh-api is a practical choice for technically proficient IoT hobbyists and developers who accept hands-on setup and ongoing operational checks. Expect to stage incremental tests and to validate automated interactions before wider use. Practical advice: run integrations in a controlled test network, confirm message flows step by step, and maintain a spare node for command verification to reduce operational risk.
