EvoBurrow MCP server
io.github.daredoole/evoburrow-mcp·v2.0.0-beta.1·7 starsUnofficial guarded A1 Evo AcoustiX, REW, and Denon/Marantz calibration tools.
7 stars
Reviews
Write oneNobody has reviewed EvoBurrow MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
EvoBurrow MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How EvoBurrow MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,243 servers
- GitHub stars
- 7
- more than 86% of 28,706 servers
Install EvoBurrow MCP in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the EvoBurrow MCP repository's README, as published. We do not edit it. Read it on GitHub
EvoBurrow MCP
A careful little control room for A1 Evo AcoustiX and Denon/Marantz AVRs.
EvoBurrow is an unofficial, cross-platform Model Context Protocol (MCP) server for A1 Evo AcoustiX, Room EQ Wizard (REW), Audyssey calibration artifacts, and Denon/Marantz AVR control. It inspects calibration files, runs protected measurements, coordinates Speaker Preset 1/2, and makes allowlisted LAN changes with backups and verification.
It is not affiliated with or endorsed by OCA, A1 Evo AcoustiX, Audyssey, Denon, or Marantz. A1 Evo remains the owner of measurement, optimization, and calibration transfer.
Choose the right audio MCP
The projects are complementary, but intentionally separate: EvoBurrow owns AVR-specific safety and A1 context; Audio Calibration MCP stays hardware-neutral.
What lives in the burrow
- Inspect and compare .ady, .oca, .avr, .mdat, HTML reports, target curves, and session logs.
- Diagnose measurement repeatability, polarity, timing, crossover headroom, subwoofer integration, and speaker geometry.
- Discover or start REW on Windows, macOS, and Linux, negotiate its local API, protect sweeps, save/load MDAT files, and analyze phase-aware crossover summation and multiseat consistency.
- Read Denon/Marantz status, decode protocol responses, snapshot the AVR, preview exact diffs, execute only allowlisted changes after confirmation, and verify the result.
- Catalog A1 calibration files and bind their hashes to Denon Speaker Preset 1/2 without confusing presets with Quick Select buttons.
- Run A1's terminal workflow only through a hash-bound, locked, time-limited adapter with saved transcripts.
Generic car, laptop, JamesDSP, FIR-laboratory, and listening-test workflows intentionally remain in Audio Calibration MCP.
Safety model
Read-only inspection comes first. Receiver writes, A1 terminal runs, file loads, target creation, and REW startup use explicit plans or confirmation. Arbitrary AVR protocol strings and undocumented calibration uploads are not exposed. Backups and post-change verification are part of the workflow, not optional cleanup.
EvoBurrow cannot make a calibration “perfect,” certify standards compliance, or derive listening preference from a graph. It separates measured facts, calculations, engineering interpretation, and community reports.
Requirements
- Node.js 20 or 22
- A local A1 Evo AcoustiX workspace and supported executable
- REW with its local API enabled on 127.0.0.1:4735 for live measurement tools
- A Denon/Marantz receiver reachable on the local network for AVR tools
Install and run
npm ci
npm run build
npm startThe Codex plugin manifest is in .codex-plugin/plugin.json; .mcp.json launches the bundled stdio server. A1EVOHOME, A1REWURL, and A1REWEXECUTABLE can override local discovery when needed.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
EvoBurrow MCP: common questions
- Is EvoBurrow MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the EvoBurrow MCP safety report
- Does EvoBurrow MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is EvoBurrow MCP maintained?
- The last commit was 10 days ago (2026-10-26). The latest release is v2.0.0-beta.1.
- How does EvoBurrow MCP compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,243 servers); github stars 7 (more than 86% of 28,706 servers). Full comparison.