room-eq-wizard-mcp

An MCP server that connects LLMs to Room EQ Wizard (REW): typed control of REW's HTTP API plus local acoustic analysis that reduces measurement data to something a model can reason about.

REW is the DSP engine — sweeps, RT60, averaging, EQ optimization all run inside REW, and this server drives them through the API. What the server adds is the layer REW doesn't have: peak/null detection with Q factors and severity, per-band statistics, before/after comparison, room-mode prediction correlated against measurements, and log-decimated curves sized for an LLM context instead of megabytes of base64.

Requirements

• Node.js 20+

• REW 5.40+ running with its API server enabled:

  • macOS: open -a REW.app --args -api

  • Windows: roomeqwizard.exe -api

  • or enable it in REW Preferences → API

• API-triggered measurement (run_sweep) additionally requires a REW Pro upgrade; every read/analysis/EQ tool works without it.

Related MCP server: AudacityMCP

Install

// Claude Desktop (claude_desktop_config.json) or any MCP client config
{
  "mcpServers": {
    "rew": {
      "command": "npx",
      "args": ["-y", "room-eq-wizard-mcp"]
    }
  }
}

# Claude Code
claude mcp add rew -- npx -y room-eq-wizard-mcp

The REW API address defaults to http://127.0.0.1:4735; override with the REW_API_URL environment variable if you run REW on another port.

Tools (46)

Typical session: status → run_sweep (or load_measurement_files) → analyze_response → room_mode_analysis with your room dimensions → auto_eq → compare_measurements on the predicted result.

Architecture

src/rew/       the only layer that talks to REW
  codec.ts       base64 big-endian float32 <-> arrays (REW's wire format)
  types.ts       Zod schemas — raw JSON is parsed once at this boundary
  client.ts      HTTP client; enables REW blocking mode once for long commands
src/analysis/  pure functions, no I/O, no mocks needed to test
  spectrum.ts    median-baseline peak/null detection, band stats, decimation
  room-modes.ts  rectangular-room modes, Schroeder frequency, correlation
src/tools/     MCP tools as data: one ToolDef type, one registration loop

Two properties worth knowing:

• Everything REW computes stays REW's job. RT60, averaging, EQ matching are invoked via the API, never reimplemented — the numbers you get through this server match what the REW GUI shows.

• Long commands use REW's blocking mode, enabled once per session. A sweep or EQ match returns when it finishes (client timeout 180 s). Note the blocking setting persists in REW across restarts.

Development

pnpm install
pnpm test        # unit suite (mocked HTTP) + live suite that self-skips without REW
pnpm build
pnpm typecheck

With REW running (-api), the live integration tests in src/rew/live.integration.test.ts activate automatically.

Credits

Design informed by two earlier REW MCP servers: koltyj/REW-mcp (analysis depth, typed client patterns) and KevinMeinon/rew-mcp-server (API coverage philosophy and field-tested REW payload shapes, plus its excellent REW API reference doc). REW itself is © John Mulcahy.

License

MIT