Agent-readyFeather Engine 2

An engine your AI tools can actually use.

Feather exposes 270 commands across 63 areas of the engine through a command line and an MCP server. Agents build, inspect and play-test your game through the same path as the editor.

Read the agent guide Command reference

One path for people and agents

The editor's panels and your AI tools call the same commands. Nothing an agent does bypasses validation, and nothing a person does is out of an agent's reach.

Safe by default

Every command has a strict JSON schema. Edits are validated before they apply, land in the undo history and carry a revision, so a stale agent can't overwrite newer work.

Verifiable without a window

Agents can capture the viewport to see the result, and play-test with scheduled input in a headless simulation that reports positions, score, logs and errors.

01 / Set upCLI · MCP

Connected in three steps.

01
Open your project
Launch the editor with automation enabled, or open Tools → Automation (MCP) in a running editor and choose Enable for a project folder…
02
Connect your AI client
Copy the MCP configuration from the Automation panel into any MCP-compatible client, or script the CLI directly.
03
Build together
Your agent discovers every command and its schema, makes changes you can see live in the viewport, and you undo anything you don't want.

# Discover every command and its argument schema
feather-cli catalog

# Start a live session from the editor
feather-editor --workspace . --automation .feather-session.json

# Read, then change, the open project
feather-cli --connect .feather-session.json command engine.status
feather-cli --connect .feather-session.json command scene.add \
  --json '{"kind":"Cube","name":"Crate","position":[0,2,0]}'

# Ask the editor to capture what it sees
feather-cli --connect .feather-session.json command viewport.capture \
  --json '{"path":"artifacts/view.png"}'

# Poll the job, then fetch the PNG (MCP returns it as an image)
feather-cli --connect .feather-session.json command job.inspect --json '{"job_id":1}'
feather-cli --connect .feather-session.json command viewport.image --json '{"job_id":1}'

# Play-test headlessly: walk right for one second, then check the report
feather-cli --workspace ./game --project project.feather.json \
  command game.simulate --json '{
    "frames": 240,
    "inputs": [
      {"frame": 0,  "key": "D", "pressed": true},
      {"frame": 60, "key": "D", "pressed": false}
    ]
  }'

02 / Coverage270 commands

Every feature has commands.

New engine features ship with commands, an editor panel and a headless check. These are the largest areas today.

All 270 commands

blueprint.*14
prefab.*14
landscape.*12
material.*12
project.*11
scene.*11
animation.*9
physics.*7
sequence.*7
tree.*7
viewport.*7
destruction.*6
script.*6
ai.*5
audio.*5
biome.*5
data.*5
level.*5
variables.*5
combat.*4
editor.*4
fluid.*4
game.*4
input.*4

Get startedFree · Private preview

Get early access.

Feather 2 is free and in private preview. Join the waitlist and we'll invite you as builds open up.

Or follow progress on Discord.