Connect. Control. Secure.

Mako Developer Edition: Xedge, LSP-Claw, and MQTT in mako.zip

The Mako Developer Edition is the easiest way to start Mako, Xedge, Lua Server Pages, MQTT, and AI-assisted development without assembling the environment manually.

Use this package when you want a ready-to-run development setup for Mako Server, Xedge, or the Barracuda App Server C Library. It is now the recommended path for new host-side development; manually extracting Xedge.zip from the tutorial bundle remains available for custom setups.

Using AI with the Developer Edition

The download pages include AI prompts that can help install and configure Mako Server with the Developer Edition. This is the recommended path for new users who want to use Xedge, LSP-Claw, and the included development tools with an AI agent.

Host vs. Target Development

Xedge and Mako Server are both based on the Barracuda App Server library. They provide APIs to dynamically start and stop applications while the system is running, enabling hot-swapping of persistent, long-running applications without restarting the server or device.

Host Development

When developing on a host computer, restarting the local server is often the simplest way to reload persistent applications. This also works well for AI-assisted workflows, where an AI agent can be instructed to restart the local server automatically after making changes.

Target Development, Including RTOS Development

When developing directly on an embedded device, the Xedge IDE makes development faster by letting you hot-swap applications from the Xedge UI without restarting the server or device. In addition, the LSP-Claw app, described later in this document, lets AI agents control the runtime behavior of applications developed with Xedge.

Because all of these products are based on Barracuda App Server, it is often preferable to develop part of the application on a host computer with Mako Server first. This is especially helpful for developers who are new to Real Time Logic's products and for anyone using the Mako Developer Edition described below.

Mako Developer Edition (mako.zip)

mako.zip is the resource package loaded by Mako Server at startup. Every Mako distribution includes a standard version. The Developer Edition replaces that standard package with one that includes Xedge, LSP-Claw, and MQTT development tools.

After replacing mako.zip, start Mako Server with:

What Is Included

This development build combines the standard Mako Server resource package with three developer-focused additions, already wired together:

• Xedge: a browser-based development environment for building, editing, running, and managing BAS/Mako applications.
• LSP-Claw: an MCP-enabled lab app that lets AI coding agents inspect, create, run, and debug Lua and LSP applications directly in Mako or Xedge.
• LMQTT Broker: a compact Lua MQTT 3.1.1 and MQTT 5.0 broker module from LSP-Examples, included as .lua/mqttbroker.lua for local IoT and messaging experiments.

Note: LSP-Claw can also run as an Xedge app, making it possible to use AI-assisted iterative development directly on an embedded device. Download lsp-claw.zip and install it as shown in the Xedge app installation video in the tutorial Xedge Application Deployment.

Open the Included Tools

After starting Mako Server, open:

• Xedge: http://localhost/rtl/
• LSP-Claw: http://localhost/lsp-claw/

Why Developers Should Use It

This package is designed as a low-friction starting point. Instead of extracting Xedge.zip from tutorials, cloning multiple repositories, copying hidden .lua, .config, and .preload files, and wiring applications together manually, developers can launch Mako and immediately get a working development environment.

New developers can use it to:

• Learn Mako Server and Lua Server Pages in a working runtime.
• Open Xedge immediately and experiment with server-side Lua, .xlua, LSP files, and application packaging.
• Use LSP-Claw as an AI-assisted lab for creating and testing BAS/Mako/Xedge applications.
• Start from practical examples in LSP-Examples, including REST, AJAX, WebSockets, authentication, databases, dashboards, and IoT workflows.
• Build MQTT-based prototypes using the included Lua MQTT broker module.
• Develop locally first, then apply the same BAS/Xedge patterns to embedded or RTOS deployments.

AI-Assisted Development Ready

LSP-Claw turns this package into a controlled development lab for AI agents such as Codex. Agents can connect to the running Mako/Xedge environment, inspect the runtime, work with lab files, run applications, and use trace output to debug server-side Lua and LSP code.

This makes the mako.zip Developer Edition especially useful for embedded Mako Server developers who are working from full operating systems such as Linux or QNX. Applications being tested can be restarted remotely or replaced without restarting the Mako Server.

AGENTS.md

Codex, Claude Code, Google Antigravity, and other AI agents work on a local folder. This is not directly used with LSP-Claw, but it's recommended to download and save the following file in the AI agent's current working directory, as it provides the AI agent with skills that make code generation more robust.

👉 Download Github -> LSP-Examples -> AGENTS.md

MQTT Broker Included

The included LMQTT Broker module gives developers a local MQTT test target without requiring a separate broker installation. It supports MQTT 3.1.1 and MQTT 5.0 connections, TLS and plain listeners when configured, wildcard subscriptions, authentication callbacks, and publish policy callbacks.

The broker is intended for development, testing, demos, and learning how MQTT can be integrated directly into BAS/Mako applications. It also makes it easier to design OPC UA Pub/Sub applications.

The broker includes an integrated MQTT client, so developers can build MQTT client applications without using the standard MQTT client or connecting over the loopback interface.

Security

When Mako Server starts with mako.zip Developer Edition, it binds exclusively to the loopback interface. This limits the web UI to the computer running Mako Server, so the browser and any other HTTP clients must run on the same machine.

You can disable loopback-only binding by creating a mako.conf file with the following settings:

When Mako Server loads this configuration file at startup, it binds to all interfaces, making the UI accessible from other computers.

Before enabling access from other computers in a public or untrusted environment, open Xedge and set a password. Then open LSP-Claw and set an MCP authentication token.