Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

EvoBurrow MCP

by daredooleversion 2.0.0-beta.1i★ –iRuns on your computer
Registry nameio.github.daredoole/evoburrow-mcp

Install

Overview

Description from the maker (original English)

Unofficial guarded A1 Evo AcoustiX, REW, and Denon/Marantz calibration tools.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account daredoole, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32655 servers in this category
  • Published to the registry more recently than 30% of the other 32655 servers in this category
  • Basic checks equal to or better than 100% of the other 32655 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is EvoBurrow MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.0-beta.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Use this project when you needUse Audio Calibration MCP when you need
A1 Evo AcoustiX artifact inspection or terminal workflowsGeneral REW measurement and room/speaker analysis
Denon/Marantz AVR status, preset mapping, backup, or guarded LAN controlCar audio, powered speakers, laptop audio, or standalone DSP
Audyssey .ady/.oca calibration review tied to live AVR stateJamesDSP, CamillaDSP, Equalizer APO, FIR, or listening-test workflows

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 start

The Codex plugin manifest is in .codex-plugin/plugin.json; .mcp.json launches the bundled stdio server. A1_EVO_HOME, A1_REW_URL, and A1_REW_EXECUTABLE can override local discovery when needed.

MCP configuration
{

"mcpServers": { "a1-evo-audio-expert": { "command": "node", "args": ["/absolute/path/to/evoburrow-mcp/dist/server.mjs"] } } }

The compatibility server key stays a1-evo-audio-expert so existing clients do not lose their tool namespace. The public project and package name is EvoBurrow MCP.

Recommended workflow

  1. Scan the workspace and inspect the latest artifacts.
  2. Probe REW and the AVR without changing anything.
  3. Validate measurement quality, speaker capability, crossover choices, and subwoofer integration.
  4. Let A1 generate and transfer the calibration.
  5. Snapshot and map the exact calibration to a Denon Speaker Preset.
  6. Run protected post-calibration measurements and a level-matched comparison.
  7. Preserve the baseline and report uncertainty or missing evidence plainly.

Privacy

There is no telemetry. Local artifacts may contain receiver IP addresses, usernames, absolute paths, room geometry, microphone metadata, and calibration fingerprints. Do not publish measurements, backups, transcripts, or receiver snapshots without reviewing and redacting them.

Development

npm test builds the server and runs hardware-independent tests. npm run validate:release checks package/plugin metadata and the bundled MCP surface. Hardware smoke tests must remain opt-in and must never run in normal CI.

See SECURITY.md, CONTRIBUTING.md, and CHANGELOG.md.

Releases are built and tested from pinned GitHub Actions. Tag workflows produce an npm-compatible tarball plus a GitHub build-provenance attestation; npm publication remains a separate, explicitly configured step.

Support the project

EvoBurrow is free and open source. If this little bunny saves your calibration from a bad day, you can buy daredoole a coffee.

Ask PopNx