APPLIED MANIFOLD // SPATIAL COMPILER v0.4.2

MODULE: PYROHEADLESS GPUSAME SPEC, SAME BYTES

Applied Manifold The spatial compute cloud for 3D reality

Let your agents ship 3D without opening Blender

The compiler for 3D

Send a raw mesh or a pyro spec over MCP or REST. Get back assets ready for production and simulation, plus a JSON report your code can check.

Give this to your agent : Claude Code, Codex, Cursor, others
$ set up Spatial Compiler - https://appliedmanifold.com/llms.txt
Full agent prompt

Connect the Spatial Compiler MCP server for this project: add the hosted server https://mcp.spatialcompiler.dev, or run `npx -y @spatial-compiler/mcp` with my API key in SPATIAL_API_KEY. Read appliedmanifold.com/llms.txt, then use its tools for 3D assets in this project.

VIEWPORT // DECIMATE.LIVELOD 0/4
STATIC FRAME · WEBGL UNAVAILABLE TRIS 81,920 → 81,920
Mesh decimation demo, drawn live in your browser.

Headless GPU compilation for 3D geometry and physics

3D tools assume a person at a desktop viewport. Agents that drive them by screenshot are slow and still ship broken topology.

Spatial Compiler is a headless GPU kernel your agents call over MCP or REST. No window, no editor: call it in a loop and check every result in code.

Built for

Four pipelines that turn raw geometry into machine-ready assets.

All use cases →

Built for autonomous loops

Spatial Compiler (@spatial-compiler/mcp) gives Claude Code, Cursor or your CI a GPU co-processor for 3D, over MCP or REST. One endpoint from raw asset to shipped asset.

Operations reference → Pyro module → Use cases →

  • compile_3d_asset (Geometry & Materials)

    Welds non-manifold edges, decimates to exact triangle budgets (meshoptimizer), packs UV atlases (xatlas) and bakes channel-packed ORM textures.

  • pyro (Fire, smoke, explosion, dust)

    Bakes fire, smoke, explosion and dust flipbooks from a .pyro.toml spec, lit from six directions for relighting.

  • wire (Godot 4)

    Installs the six-way shader in a Godot project and writes a ready scene per bake.

SPEC // FIRE_WHIRL.PYRO.TOMLEXCERPT
# The spin: around the vertical axis, up the whole column, on air and gas alike.
[[forces]]
kind = "vortex"
shape = "box"
position_m = [0, 4, 0]
size_m = [1.3, 4, 1.3]
direction = [0, 1, 0]
strength = 14
max_speed_mps = 4
falloff = 0.4
Fire whirl example: one vortex force spins the column.
FIRE_WHIRLFINAL · 0.4.2
First frame of the fire_whirl bake
Fire whirl, 4.4 x 7.1 m. Spec →
FIREBALLFINAL · 0.4.2
First frame of the fireball bake
Fireball, 9.4 x 13.4 m. Spec →
SMOKE_PLUMEFINAL · 0.4.2
First frame of the smoke_plume bake
Smoke plume, 7.0 x 10.8 m. Spec →
IMPACTFINAL · 0.4.2
First frame of the impact bake
Impact, 3.5 x 2.8 m. Spec →
WINDOW_FIREFINAL · 0.4.2
First frame of the window_fire bake
Window fire, 3.9 x 4.7 m. Spec →
DUST_RINGFINAL · 0.4.2
First frame of the dust_ring bake
Dust ring, 10.5 x 2.2 m. Spec →

Pay per operation, start free

New accounts get $5 of usage. A sweep is $0.20. See pricing tiers →

Connect your agent

mcp.json · hosted
{
  "mcpServers": {
    "spatial-compiler": {
      "type": "http",
      "url": "https://mcp.spatialcompiler.dev"
    }
  }
}

Paste one of these into your agent, then ask it for a bake. Connection guide →

TELEMETRY FIELDS
status
dry_run
tris_in
target_tris
tris_out
draw_calls
vram_bytes
elapsed_ms
cache
cost_usd_est

Every compile returns these fields. Telemetry fields →

README.FAQ
What is Spatial Compiler?

A GPU compiler for 3D assets. Send raw .glb or CAD geometry over MCP or REST; get back decimated, UV-packed, physics-ready assets and JSON telemetry. The pyro module bakes fire, smoke, explosion and dust flipbooks from a spec.

Why not drive a desktop 3D tool from an agent?

Spatial Compiler has no window. An agent runs it as a command and checks a JSON report and one preview image. Errors name the nearest valid key, and every warning names the setting to change.

Is Spatial Compiler a 3D generator?

No. It compiles meshes and specs you already have. Call it on each output of your text-to-3D or image-to-3D model.