English Français العربية

io.github.ynishi/mlua-swarm

Registre officiel IA et agents

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

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
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mlua-swarm": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/ynishi/mse:0.32.1",
                "mcp"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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.

Questions fréquentes

Qu'est-ce que io.github.ynishi/mlua-swarm ?

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

Comment installer io.github.ynishi/mlua-swarm ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mlua-swarm -- docker run -i --rm ghcr.io/ynishi/mse:0.32.1 mcp. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.ynishi/mlua-swarm ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.ynishi/mlua-swarm est-il open source ?

Oui. Son code est sur GitHub sous licence Apache-2.0.

Qui maintient io.github.ynishi/mlua-swarm ?

Il est publié par ynishi. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.