English Français العربية

io.github.ynishi/mlua-swarm

Official registry AI and agents

MCP server for mlua-swarm: engine that compiles flow.ir Blueprints and dispatches agent steps.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

OCI package ghcr.io/ynishi/mse:0.32.1
Claude Code 
claude mcp add mlua-swarm -- docker run -i --rm ghcr.io/ynishi/mse:0.32.1 mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mlua-swarm": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/ynishi/mse:0.32.1",
                "mcp"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mlua-swarm
  2. Install
  3. Documentation
  4. Workspace crates
  5. License

mlua-swarm

A long-running swarm engine host that compiles flow.ir Blueprints and dispatches their agent steps to workers. A Blueprint declares a flow (step / seq / branch / loop / fanout / try / let nodes) plus the agents it references; the engine resolves each agent to a backend (in-process Lua, a Rust function, a child process, or an interactive Operator) and drives the flow while recording task state.

Install

cargo install mlua-swarm-cli

This installs the mse binary with two subcommands:

mse serve   # HTTP + WS server (tasks, Blueprint store, WS Operator sessions)
mse mcp     # MCP adapter over stdio, for AI agents (Claude Code etc.)

One-shot Blueprint execution is available through the swarm_run MCP tool (exposed by mse mcp), which runs through the canonical TaskApplication.handle / TaskLaunchService::launch path.

MCP client config:

{ "command": "mse", "args": ["mcp"] }
Docker (no Rust toolchain required)

Also listed on the MCP Registry as io.github.ynishi/mlua-swarm:

{
  "mcpServers": {
    "mlua-swarm": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "ghcr.io/ynishi/mse:latest",
        "mcp"
      ]
    }
  }
}

Documentation

Documentation is served from the code itself:

  • API / architecture — rustdoc on docs.rs (the crate root doc is the architecture overview).
  • Guides / samples / schema — bundled MCP resources under mse://, served by mse mcp and always version-matched to the binary: mse://guides/getting-started, mse://guides/bp-lifecycle (the develop → trial-run → operate workflow map), mse://guides/blueprint-authoring, mse://guides/mcp-tool-reference, mse://blueprints/samples/*, and the live Blueprint JSON Schema at mse://api/blueprint-schema (also available as the bp_schema tool).

Workspace crates

craterole
mlua-swarmengine core (workspace root package)
mlua-swarm-schemaBlueprint schema types
mlua-swarm-serverHTTP + WS server library
mlua-swarm-clithe mse binary

License

Licensed under either of Apache License 2.0 or MIT License at your option.

Frequently asked questions

What is io.github.ynishi/mlua-swarm?

MCP server for mlua-swarm: engine that compiles flow.ir Blueprints and dispatches agent steps.

How do I install io.github.ynishi/mlua-swarm?

It runs on your machine. In Claude Code: claude mcp add mlua-swarm -- docker run -i --rm ghcr.io/ynishi/mse:0.32.1 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.ynishi/mlua-swarm need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.ynishi/mlua-swarm open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains io.github.ynishi/mlua-swarm?

It is published by ynishi. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.