Webear MCP Server

Give your AI coding assistant ears — capture, analyze, and describe live audio.

Remote serverstreamable-httpGo

What is the Webear MCP server?

Connect Webear to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Give your AI coding assistant ears — capture, analyze, and describe live audio. The webear mcp server is what makes that connection.

What the server does

An MCP server + browser SDK that gives AI coding assistants direct sensory access to a live web application. Audio, visuals, performance, network, security, and console — captured from the browser, analyzed in real time, delivered via MCP.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Sensor — Tool
  • Ear — capture_audio
  • Eye — capture_video
  • Sense — capture_telemetry
  • Nerve — capture_nerve
  • Shield — capture_shield
  • Log — capture_logs
  • analyze_audio — ── Loudness ───────────────────────────────────────── RMS: -12.4 dBFS Peak: -1.2 dBFS Dynamic range: 11.2 dB Crest factor: 3.63 Clipping: none
  • diff_audio — ── Loudness ────────────────────────────────────────── RMS: -14.2 dBFS → -12.4 dBFS (+1.8 dBFS) ⚠ Peak: -3.1 dBFS → -0.2 dBFS (+2.9 dBFS) ⚠ CLIPPING

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: WEBEAR_BASE_URL, CODEDSWITCH_API_KEY, MCP_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js >= 18 - A browser that supports MediaRecorder (Chrome, Firefox, Edge, Safari 14+) - A CODEDSWITCH_API_KEY for analysis (free at codedswitch.com) ---

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Webear's toolset — Sensor, Ear, Eye and 6 more — is a fair guide to whether it matches your workflow. It is maintained by asume21; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Webear's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Webear.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
SensorTool
Earcapture_audio
Eyecapture_video
Sensecapture_telemetry
Nervecapture_nerve
Shieldcapture_shield
Logcapture_logs
analyze_audio── Loudness ───────────────────────────────────────── RMS: -12.4 dBFS Peak: -1.2 dBFS Dynamic range: 11.2 dB Crest factor: 3.63 Clipping: none
diff_audio── Loudness ────────────────────────────────────────── RMS: -14.2 dBFS → -12.4 dBFS (+1.8 dBFS) ⚠ Peak: -3.1 dBFS → -0.2 dBFS (+2.9 dBFS) ⚠ CLIPPING INTRODUCED — gain staging regression

How to install the Webear MCP server

**Cursor** (`.cursor/mcp.json`):
```json
{
  "mcpServers": {
    "webear": {
      "command": "npx",
      "args": ["webear"],
      "env": {
        "WEBEAR_BASE_URL": "http://localhost:5000",
        "CODEDSWITCH_API_KEY": "your-key-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= 18 - A browser that supports MediaRecorder (Chrome, Firefox, Edge, Safari 14+) - A CODEDSWITCH_API_KEY for analysis (free at codedswitch.com) ---
VariableDescriptionRequired
WEBEAR_BASE_URLEndpoint or connection string the server talks to.Yes
CODEDSWITCH_API_KEYCredential the server authenticates with.Yes
MCP_API_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Webear to Sensor.
  • Use Webear to Ear.
  • Use Webear to Eye.

Frequently asked questions

It connects Webear to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (Sensor, Ear, Eye, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Webear directly.