impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Render, analyze, and verify audio (WAV/FLAC/mp3/ogg) offline and deterministically via MCP tools.
Skills that teach the AI this kind of work; they work alongside this one
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 14/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 22/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Cochlea and tell me what you can do for me, then show me one thing✓ If Claude says it is using Cochlea or shows a Cochlea tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Cochlea yet
Cochlea runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Cochlea
B · Others in Design, images & audio that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Cochlea yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Cochlea
Cursor cannot connect Cochlea yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Cochlea
VS Code cannot connect Cochlea yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Cochlea
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 19, 2026
The registry name was verified with the GitHub account richer-richard, which owns the repo
Code last changed 2 months ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/richer-richard-cochlea-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 2 months ago, and the latest version (0.7.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| This one Cochlea | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| License | Apache-2.0 | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
A headless audio engine for agents. Write a score as data, render it offline to deterministic PCM, then *listen through numbers* — loudness, onsets, pitch, key, spectrograms — and assert what you heard. Compose → render → probe → verify, with no human ear (and no audio device) in the loop.
*What the agent sees: the mel spectrogram of examples/scores/first_light.ron — the score used in the example below — after render and probe. No PCM in sight.*
use cochlea_score::*;
let score = Score::new(SampleRate(48_000), Ppq(960)) .time_signature(4, 4) .tempo(Ticks(0), Bpm(120.0)) .track("lead", Instrument::preset("saw_lead")) .note("lead", bar(1).beat(1), Dur::quarter(), Pitch::A4, Vel(96)) .automate("lead", Param::CUTOFF_HZ, keys![(bar(1), 400.0, ease_in_out()), (bar(3), 4_000.0)]);
let rendered = cochlea_render::render(&score)?; rendered.write_wav("mix.wav")?;
use cochlea_verify::{VerifyExt, Tol, Ms, Cents, Db}; let report = rendered.verify(&score) .true_peak_below(-1.0) .pitch_matches_score("lead", Cents(10.0)) .monotone("lead", Param::CUTOFF_HZ, bar(1)..bar(3)) .silent_after(bar(5)) .run(); assert!(report.passed);
Or entirely from the command line, score as RON:
cochlea render score.ron --out mix.wav --stems stems/ --verify
cochlea probe input.wav --json report.json --spectro spec.png cochlea probe input.wav --digest --window-ms 500 cochlea probe input.mp3 --from 42.0 --to 44.5 # zoom into a window, any format cochlea diff a.wav b.wav --tier2 --spectro delta.png cochlea lint score.ron cochlea spectro input.wav --out spec.png --annotate # draw beats/onsets/pitch on the image cochlea import song.mid --out score.ron # SMF -> score, timing exact cochlea transcribe solo.wav --out score.ron # audio -> score, the inverse of render cochlea reference # the full score-authoring reference, generated from the live preset bank
cochlea probe works on any WAV, plus FLAC (decoded bit-exact), mp3, and ogg — still without ffmpeg, and with no score required. That's the front door: point it at audio you didn't render, and you get the same JSON report and spectrogram an agent uses to review its own work.
compose → render → probe (JSON) → spectrogram (one vision call) → verify
cochlea render score.ron --out mix.wav.cochlea probe mix.wav --json report.json. No image, no audio: the agent reads numbers.cochlea spectro mix.wav --out spec.png renders one small PNG the agent reviews in a single vision call instead of reasoning about raw samples.cochlea render score.ron --verify runs the score's embedded assertions and exits nonzero on failure. An agent can retry on its own, without a human confirming "yes, that sounds right."When something in the middle of a long file needs a closer listen, every read tool takes --from/--to. Probe just bars 17–19, or draw a spectrogram of just the drop. The cut is frame-exact, report times are relative to it, and source.start_ms records where it came from. That turns the whole stack into a zoom lens instead of a whole-file-only report.
The economics are the point here, not an afterthought. The first_light render above is 7 seconds of 48 kHz 32-bit-float PCM, which is 2.7 MB. A 3-minute piece at the same settings runs about 66 MB. You would not hand that to an agent as text, and reading it sample by sample is worse.
Its probe report is a few KB of JSON instead. Here is schema v5, trimmed to the interesting fields. Note pitch.melody: the piece's bass line and melody read back as *note events*, which is the read-back half of the compose loop.
{
"schema_version": 5, "source": { "sample_rate": 48000, "channels": 2, "duration_ms": 7035.708333333333, "start_ms": 0.0 }, "loudness": { "integrated_lufs": -22.700454879284784, "true_peak_dbtp": -15.910817022082783, "lra": 10.607660373688798 }, "onsets": { "count": 6, "times_ms": [1077.33, 2149.33, 2346.67, 3221.33, 4538.67, 5034.67] }, "pitch": { "voiced_ratio": 0.9847560975609756, "median_f0_hz": 110.00194603797897, "melody": [ { "name": "A2", "start_ms": 0.0, "end_ms": 1045.3, "cents_off": 0.1 }, { "name": "E2", "start_ms": 1077.3, "end_ms": 2112.0, "cents_off": 0.3 }, { "name": "F#2", "start_ms": 2154.7, "end_ms": 3178.7, "cents_off": 0.2 }, { "name": "E2", "start_ms": 3210.7, "end_ms": 4384.0, "cents_off": 0.3 }, { "name": "E5", "start_ms": 4394.7, "end_ms": 5813.3, "cents_off": -0.4 } ] }, "timbre": { "mfcc_mean": [-37.64, 14.47, -4.44, 1.24, "..."], "mfcc_std": ["..."], "frames": 656 }, "key": { "tonic": "E", "mode": "major", "confidence": 0.8093960265638273 }, "tempo": { "bpm": 55.97014925373134, "confidence": 0.6633739386089712, "stability": 0.3333333333333333, "candidates": [ { "bpm": 55.97014925373134, "salience": 0.6633739386089712 }, { "bpm": 112.5, "salience": 0.21588204941945222 } ] }, "rhythm": { "grid_alignment": 0.8333333333333334, "grid": "straight", "offbeat_ratio": 0.4, "clear_rhythm": true }, "stereo": { "width": 0.02967719705208343, "correlation": 0.9981362354107913, "balance": -0.0016380539212361243 }, "structure": { "section_count": 1, "confidence": 0.0 }, "silence": { "trailing_ms": 2485.708333333333 }, "clipping": { "clipped_samples": 0, "true_peak_over_0dbtp": false } }
And the spectrogram is one small image. Here's the title_cue demo — a pad whose cutoff_hz automation sweeps 250 Hz → 5000 Hz across bars 1–3:
*The dark band at the top of the frame narrows as the sweep runs, letting more high-frequency energy through over time. An agent reads that straight off the image. The demo's Monotone(track: "pad", param: "cutoff_hz", ...) assertion checks the same thing numerically.*
To get a whole piece in one image no matter how long it is, --sheet tiles the spectrogram into a contact sheet instead of one long strip. Two bars per tile here, via --bars-per-tile 2:
probe --digest skips JSON and prints a deterministic text summary instead: one line per feature dimension, then a windowed timeline capped at about 40 rows. Here's real output for the drum_groove demo — 20.8 seconds and four tracks, with the rhythm, stereo, and structure dimensions all in one screenful:
cochlea digest: 20.755s 2ch 48000Hz
loudness: integrated=-24.06 momentary_max=-22.42 true_peak=-5.95 lra=1.61 key: A# minor (conf 0.54) pitch: voiced=23% median=63.8Hz (C2 -42.8c) melody: 6 notes C2 C2 C2 C2 A1 A1 tempo: 110.3bpm (conf 0.79, stability 1.00) alts: 54.9bpm(0.89), 36.6bpm(0.79) rhythm: clear=true grid_align=0.98 (straight) offbeat=0.56 stereo: width=0.07 corr=0.99 bal=-0.01 structure: 1 section onsets: count=58 rate=2.79/s silence: leading=0ms trailing=2545ms clipping: clipped=0 over_0dbtp=false timeline: window=1000ms bucket=1x rows=21 idx t(s) rms peak ons f0 flags 0 0.000-1.000 -25.55 -7.36 4 64.0 - 1 1.000-2.000 -25.61 -8.37 3 63.4 - ...
Tempo and rhythm are reported as *separate axes*, because they change independently. A drum solo can hold a rock-steady pulse while its pattern turns unrecognizable, and that difference is exactly what an agent needs to see.
Here the tempo reads 110.3 BPM, matching the authored 110, and stability 1.00 says the speed never moves across the piece. The alts list surfaces the genuine half-tempo reading at 54.9 BPM — which is actually the stronger raw peak, with the octave prior breaking the tie toward the beat. Metrical ambiguity like that is data an agent can weigh, rather than a coin flip hidden inside the detector.
The rhythm line then says how the *hits* relate to that pulse: 98% of onsets sit on the beat-subdivision grid and 56% land on off-beat subdivisions, so clear=true. That's an eighth-note hat groove, with its syncopation reported as a number.
Under the pre-0.2.0 metric this same groove read clear_rhythm=false at confidence 0.01. Layering hats, kick, snare, and pad across three metrical levels diluted every lag's share of a mass-fraction score. The grid-based rule asks the right question instead.
The (straight) tag is the grid *hypothesis test*: alignment is measured against both straight sixteenths and eighth-note triplets, and the report carries whichever more hits land on. A shuffle or swing take reads grid_align=1.00 (triplet) — recognized as an aligned triplet rhythm — instead of being force-fit to sixteenths and scored sloppy.
cochlea diff compares two files in feature space instead of byte-for-byte — "did my change do what I meant," not "is the file bitwise equal." Real output diffing first_light.wav against title_cue.wav:
verdict: different (duration, loudness, onsets, key)
duration a->b +1264.3 ms loudness integrated -5.95 LU true_peak +5.70 dB lra -8.88 LU onsets matched=0 mean_offset=- max_offset=- unmatched_a=6 unmatched_b=5 pitch delta +0.5 cents key a=E major (conf 0.81) b=A minor (conf 0.86) changed=true segments max_abs_rms_delta 120.99 dB at idx=7 tempo bpm -24.01 bpm stability -0.33 rhythm clear_rhythm_changed=false grid_align -0.03 grid_changed=true timbre mfcc_distance 4.00 stereo width +0.14 correlation -0.08 balance -0.01 structure section_count +0
The timbre row is an MFCC spectral-shape distance, with c0 excluded since that's just loudness. The same instrument re-rendered measures around 0, while swapping a sine for a saw at matched loudness measures well above it. It's the "did the re-render keep the instrument's character" axis, which loudness and pitch can't see.
Add --spectro delta.png and the diff also renders a signed difference heat map: red where B is louder, blue where it's quieter, black where nothing changed. A moved onset shows up as a blue/red vertical pair, and a brightened sweep as a red wedge. What changed becomes visible structure, not just a number.
Diff a render against itself, or a re-render of the same score, and the verdict reads byte-identical instead — the determinism contract above, checked from the outside. --tier2 turns that verdict into a gate: exit 0 for byte-identical or Tier-2-equivalent, exit 1 otherwise, so a CI job or an agent can catch a regression without ever reading a raw sample.
cochlea-mcp is a stdio MCP server built on the same libraries the CLI uses. It exposes twelve tools — render_score, probe_audio, spectrogram, lint_score, probe_digest, loudness_timeline, `bea