English Français العربية

Lumen

Official registry AI and agents

Cross-media conversion engine: 2D art, 3D models and engine formats, deterministic over MCP.

Source code Website 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).

MCPB package https://github.com/qompassai/lumen/releases/download/v0.1.1/lumen-mcp-0.1.1-linux-x64.mcpb

Documentation

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

Contents
  1. lumen
  2. Verified state (2026-10-01, primo)
  3. Layout
  4. License

lumen

Lux in motu — light in motion. A cross-platform, cross-media conversion engine, written in Rust (edition 2024, rmcp 3.3): one operation core that bridges media formats — 2D art and sprite formats, 3D models, and game-engine packages — converting between them deterministically from code-first records, so the same input record yields the same output on any platform. Aseprite sprites and Bevy were its first endpoints, not its purpose; the center is the factory (one identity record, emitted as 2D or 3D) and the named, verified converter chain between formats — one operation core behind three surfaces —

  • MCP tools for interactive media work: sprite operations, inspection, palettes, text, style presets, dream-animation automation, QA gates, and export backends (PNG sheets, WASM-4, TIC-80, VoidSprite file interop). All paths are project-root bounded.
  • An A2A agent surface (v0.3.x JSON-RPC) for dispatched, long-running art jobs, with the trial-then-approval art-director loop as a protocol state. See A2A_DESIGN.md.
  • A deterministic policy layer (APPA-style, adapted from archestra-ai/OpenAPPA): every tool call is checked against lumen-policy.toml before it executes, decisions are replayable, and denials name the rule they violated. See POLICY_DESIGN.md.

Companion strategy — pair, don't duplicate — is in COMPANIONS.md. How lumen was built, in what order, and under what governance (including the evidence rule its first failed build produced) is in HISTORY.md.

Verified state (2026-10-01, primo)

  • Build and clippy clean; 303 tests passed / 0 failed / 8 ignored (suite split between validation and adversarial cases).
  • Live interop gate against real Aseprite 1.3.18.6-dev and Bevy 0.18 BRP (scripts/interop_check.sh): 5 passed / 3 failed — the failures are documented premise mismatches between lumen's assumptions and the real tools' behavior; see HISTORY.md.

Layout

  • src/ — operation core: sprite_ops, inspect, palette, text, style, dream, qa, export, pipeline, policy, bevy, doc, vrm, and the a2a/ surface (mod, task, http, registry).
  • tests/ — validation and adversarial suites, incl. interop.rs (live-tool gates, ignored by default).
  • lumen-policy.toml — the shipped policy; lumen policy check and lumen policy replay are its gates.

License

This project is licensed under the Apache License, Version 2.0.

Frequently asked questions

What is Lumen?

Cross-media conversion engine: 2D art, 3D models and engine formats, deterministic over MCP.

How do I install Lumen?

Follow the installation steps in its documentation, shown on this page and in its repository.

Does Lumen 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 Lumen open source?

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

Who maintains Lumen?

It is published by qompassai. 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.