Skip to main content
Glama
README.md
# Crystalize
A FUSER MCP server. Crystalize lets an agent DJ in FUSER, Harmonix's DJ game: it searches your songs, drops discs on the decks, and changes the key and tempo, through a mod running inside the game.

## Install
Needs [uv](https://docs.astral.sh/uv/getting-started/installation/), FUSER on Steam, and UE4SS set up for it, see [Setup](docs/setup.md). Then:

```sh
git clone https://github.com/Peyton-C/Crystalize.git
cd Crystalize
uv run crystalize install
```

`install` copies the mod into FUSER and warns about anything in the setup that will crash the game or stop the mod. Crystalize looks for FUSER in Steam's default library. Pass `--game <folder>` or set `CRYSTALIZE_FUSER` if yours is elsewhere.

## Use
Start FUSER through Steam and open a freestyle session, then check the connection:

```sh
uv run crystalize state
```

Add the server to an MCP client:

```sh
claude mcp add crystalize -- uv run --directory /path/to/Crystalize crystalize mcp
```

To go straight to a campaign set or freestyle without the menus, starting FUSER if it is closed:

```sh
uv run crystalize launch --set 3.1
```

See [MCP server](docs/mcp.md) for the tools and `launch`, and [Bridge](docs/bridge.md) for how the server reaches the game.

## Clawd
Optionally, Crystalize puts Clawd, in headphones, in place of your avatar:

```sh
uv run crystalize clawd on
```

`clawd off` takes him out. See [Clawd](docs/clawd.md).

TDQS

B3.2/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct resource or action: session state vs. campaign set state, mix planning vs. playing vs. stopping, and deck-level controls are clearly separated. Potential overlaps such as get_state/get_set and drop_disc/drop_queue are explicitly differentiated in their descriptions.

Naming Consistency5/5

The tool set uses consistent snake_case verb_noun naming throughout, with clear action prefixes like get_, set_, drop_, save_, load_, list_, and play_. Minor standalone verb names like eject are still readable and fit the deck-control context.

Tool Count4/5

The 20 tools cover several genuinely distinct areas: live session control, campaign sets, song tagging/search, and mix planning/persistence. The count is on the high side but largely earned by the breadth of the DJ/mixing domain.

Completeness4/5

The surface covers most core workflows: song search/tagging, mix planning/saving/loading/playing/stopping, deck manipulation, campaign monitoring, and snapshots. A notable minor gap is the absence of a delete or remove tool for saved mixes.

Maintenance

ActivityNo data
ResponsivenessOutdated data