Webear FAQs

Question 1

What is Webear and what does it do?

Accepted Answer

Webear is an MCP (Model Context Protocol) server that gives AI coding assistants the ability to capture, analyze, and describe live audio output directly from a running web application's Web Audio API. It helps developers debug audio quality, timing, and mixing issues in real-time.

Question 2

What are the basic requirements to start using Webear?

Accepted Answer

To use Webear, you'll need Node.js (version 18+), a modern browser that supports MediaRecorder, and a free CODEDSWITCH_API_KEY for analysis. Installation involves adding Express middleware to your dev server and a client-side snippet to your web app.

Question 3

What specific audio insights can Webear provide?

Accepted Answer

Webear offers detailed signal analysis, including RMS, peak dB, clipping detection, spectral centroid, frequency band breakdown (sub, bass, mid, hi-mid, high), BPM estimation, and timing jitter. It also generates plain-English AI descriptions and can compare two audio captures to flag changes.

Question 4

How does Webear's audio capture differ from using a microphone?

Accepted Answer

Unlike a microphone, Webear taps the Web Audio API output directly before it reaches your speakers. This provides a clean, digital signal, free from room acoustics, microphone hardware artifacts, or any ambient noise, ensuring precise analysis of your application's sound.

Question 5

Is Webear compatible with different web audio frameworks and setups?

Accepted Answer

Yes, Webear is designed for broad compatibility. It integrates seamlessly with raw Web Audio API contexts, Tone.js projects, and Three.js WebGL game audio setups, making it versatile for various web audio development environments.

Webear

Webear

Key Features

Use Cases

Key Features

Use Cases