Skip to main content
ClaudeWave

Lux in motu - MCP server for Aseprite sprite artistry with Bevy live-world interop

MCP ServersOfficial Registry0 stars0 forks● RustApache-2.0Updated today
ClaudeWave Trust Score
87/100
✓ Trusted
Passed
  • ✓Open-source license (Apache-2.0)
  • ✓Actively maintained (<30d)
  • ✓Clear description
  • ✓Documented (README)
Last scanned: 10/21/2026
Install in Claude Code / Claude Desktop
Method: Manual · lumen
Claude Code CLI
git clone https://github.com/qompassai/lumen
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "lumen": {
      "command": "lumen"
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Install the binary first: cargo install lumen (or build from https://github.com/qompassai/lumen).
Use cases

MCP Servers overview

# 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 —
<a href="./LICENSE"><img src="https://img.shields.io/badge/License-Apache%202.0-blue.svg" alt="License: Apache 2.0"></a>
<a href="https://doi.org/10.5281/zenodo.23503518"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.23503518.svg" alt="DOI"></a>

- **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](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](POLICY_DESIGN.md).

Companion strategy — pair, don't duplicate — is in
[COMPANIONS.md](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](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](./LICENSE).

What people ask about lumen

What is qompassai/lumen?

+

qompassai/lumen is mcp servers for the Claude AI ecosystem. Lux in motu - MCP server for Aseprite sprite artistry with Bevy live-world interop It has 0 GitHub stars and its last recorded update is dated 2026-10-21.

How do I install lumen?

+

You can install lumen by cloning the repository (https://github.com/qompassai/lumen) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is qompassai/lumen safe to use?

+

Our security agent has analyzed qompassai/lumen and assigned a Trust Score of 87/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.

Who maintains qompassai/lumen?

+

qompassai/lumen is maintained by qompassai. The last recorded GitHub activity is dated 2026-10-21, with 0 open issues.

Are there alternatives to lumen?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy lumen to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: qompassai/lumen
[![Featured on ClaudeWave](https://claudewave.com/api/badge/qompassai-lumen)](https://claudewave.com/repo/qompassai-lumen)
<a href="https://claudewave.com/repo/qompassai-lumen"><img src="https://claudewave.com/api/badge/qompassai-lumen" alt="Featured on ClaudeWave: qompassai/lumen" width="320" height="64" /></a>

More MCP Servers

lumen alternatives