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

MCP Listen

by decibriversion 0.7.2i★ –iRuns on your computer
Registry nameio.github.decibri/mcp-listen

Install

Overview

Description from the maker (original English)

Give your AI agents the ability to listen. Microphone capture and speech-to-text.

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: Design, images & audio

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.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

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

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "listen": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-listen"
      ]
    }
  }
}

Run this in your terminal

claude mcp add listen -- npx -y mcp-listen

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "listen": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-listen"
      ]
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "listen": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcp-listen"
      ]
    }
  }
}

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 decibri, 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 Design, images & audioi

  • More stars than 0% of the other 2204 servers in this category
  • Published to the registry more recently than 54% of the other 2204 servers in this category
  • Basic checks equal to or better than 100% of the other 2204 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 MCP Listen 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 (0.7.2) reached the registry 25 days ago.

Which apps can use it?

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

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

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

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

Runs on your computer★ 16,165MITUpdated 5 months ago
Install

Claude Real Video

by HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

Runs on your computer★ 2,284MITUpdated 2 months ago
Install

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.

Runs in the cloud★ 2,152Updated 13 months ago
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.

mcp-listen

Give your AI agents the ability to listen

Microphone capture and speech-to-text tools for MCP-compatible agents.

Meta

Tools

ToolDescription
list_audio_devicesList available microphone input devices
capture_audioRecord audio from the microphone and save as WAV
voice_queryCapture, transcribe on this machine (whisper.cpp), and query a model through the local Ollama daemon

Quick Start

Claude Code
claude mcp add mcp-listen npx mcp-listen
Claude Desktop / ChatGPT Desktop / Cursor / Windsurf / VS Code

Add to your MCP configuration:

{

"mcpServers": { "mcp-listen": { "command": "npx", "args": ["-y", "mcp-listen"] } } }

Compatible with Claude Desktop, ChatGPT Desktop, Cursor, GitHub Copilot, Windsurf, VS Code, Gemini, Zed, and any MCP-compatible client.

Global Install
npm install -g mcp-listen

Requirements

Supported platforms:

  • Windows x64
  • macOS Apple silicon (arm64)
  • Linux x64 and arm64 (glibc)

Intel Mac (darwin-x64) is not supported: Apple has discontinued the platform and no decibri binary is published for it.

For `list_audio_devices` and `capture_audio`:

  • Node.js 18+
  • A microphone

For `voice_query` (optional):

  • Ollama running locally
  • Whisper GGML model (see Whisper Model Setup)

Tool Reference

Arguments are validated before anything is recorded or written. An argument a tool does not declare is rejected with an error naming it, rather than silently ignored. duration_ms must be an integer between 100 and 30000; silence_ms an integer between 100 and 10000; stop_on_silence a boolean; device a non-negative integer index or a non-empty string id from list_audio_devices. A silence_ms that cannot take effect (passed without silence-stopping active) is rejected for the same reason unknown arguments are. A rejected call writes nothing to disk.

list_audio_devices

Returns a JSON array of available audio input devices.

Parameters: None

Example response:

[

{ "index": 0, "name": "Microphone", "id": "wasapi:{0.0.1.00000000}.{00000000-0000-0000-0000-000000000001}", "maxInputChannels": 2, "defaultSampleRate": 48000, "isDefault": true }, { "index": 1, "name": "Microphone Array", "id": "wasapi:{0.0.1.00000000}.{00000000-0000-0000-0000-000000000002}", "maxInputChannels": 2, "defaultSampleRate": 48000, "isDefault": false } ]

The id is stable across reboots and device changes. The index is positional and can shift when devices are added or removed, and names are not unique. Prefer id when selecting a device. In the rare case the host cannot produce a stable id for a device, its id is an empty string and it can only be selected by index.

capture_audio

Records audio from the microphone and saves as a WAV file. Records for exactly duration_ms by default, or until the speaker stops talking with stop_on_silence: true.

Parameters:

ParameterTypeDefaultDescription
duration_msnumber5000Recording duration in milliseconds (100-30000). A maximum, not an exact length, when stop_on_silence is true
devicenumber or stringsystem defaultDevice index or stable device id from list_audio_devices
stop_on_silencebooleanfalseStop when the speaker stops talking, detected with on-device voice activity detection (Silero VAD, bundled, no download)
silence_msnumber1000Continuous silence in milliseconds that ends a stop_on_silence recording (100-10000). Requires stop_on_silence: true

Example response (fixed duration):

{

"path": "/tmp/mcp-listen-1712345678901.wav", "duration_ms": 5000, "sample_rate": 16000, "channels": 1, "size_bytes": 160044 }

Example response (`stop_on_silence: true`):

{

"path": "/tmp/mcp-listen-1712345678901.wav", "duration_ms": 2600, "sample_rate": 16000, "channels": 1, "size_bytes": 83244, "stopped_by": "silence", "speech_detected": true }

With stop_on_silence, duration_ms in the response is the actual captured length, and stopped_by says how the recording ended: "silence" (the speaker finished), "ceiling" (the duration_ms maximum was reached), or "no_speech_timeout" (nobody spoke for 10 seconds; the WAV is still returned, with speech_detected: false, so silence is a reported outcome rather than an error). Detection runs per ~100ms audio buffer, so the effective hangover rounds up to the next buffer, and the recording keeps everything from the start of the call through the stop decision: nothing is gated or clipped at speech boundaries, and the audio itself is byte-identical to a fixed-duration capture of the same sounds.

voice_query

Full voice pipeline: capture audio, transcribe it on this machine with whisper.cpp, send the transcription to the local Ollama daemon, and return the transcription and the response. The audio stays on this machine. Recording stops automatically when the speaker stops talking; pass stop_on_silence: false for a fixed-length recording.

Parameters:

ParameterTypeDefaultDescription
duration_msnumber15000 / 5000Maximum recording duration in milliseconds (100-30000). Default 15000 while silence-stopping is active, 5000 with stop_on_silence: false
devicenumber or stringsystem defaultDevice index or stable device id from list_audio_devices
stop_on_silencebooleantrueStop recording when the speaker stops talking. Pass false to record for exactly duration_ms
silence_msnumber1000Continuous silence in milliseconds that ends the recording (100-10000)
whisper_modelstringggml-base.en.binPath or filename of Whisper GGML model
languagestringenLanguage code for transcription
modelstringllama3.2Ollama model name
promptstringYou are a helpful assistant.System prompt for the LLM

Example response:

{

"transcription": "What is the default port for PostgreSQL?", "response": "PostgreSQL runs on port 5432 by default.", "model": "llama3.2" }

Result outcomes. voice_query reports five distinct outcomes. The structured fields are the contract (isError, speech_detected, transcription); any message is a human-readable hint whose wording is not part of the contract, so a caller branches on the fields, never on the prose. The rule is simple: if the pipeline ran, the result is a success (even when it found no words); if a dependency broke, the result is an error.

OutcomeisErrorspeech_detectedtranscriptionresponse
Normalabsentabsentthe textthe answer
No speech at allabsentfalsenullnull
Speech, but no transcribable wordsabsenttrue (absent with stop_on_silence: false)nullnull
Transcription step failedtrueabsentabsentabsent
Ollama unavailable, errored, or emptytrueabsentabsent (the text if the reply is empty)absent (null if the reply is empty)

A caller distinguishes "the user was silent" from "the user spoke but produced no words" by speech_detected (false vs true), both carrying transcription: null. Non-speech audio never reaches the language model: whisper's non-speech markers ([BLANK_AUDIO], [MUSIC], (silence), and similar) are treated as no usable words rather than sent on as a query.

No speech (speech_detected: false):

{

"speech_detected": false, "stopped_by": "no_speech_timeout", "transcription": null, "response": null, "message": "No speech was detected. Ask the user to repeat, or check that the correct microphone is selected." }

Speech, but no transcribable words (speech_detected: true, transcription: null):

{

"speech_detected": true, "stopped_by": "silence", "transcription": null, "response": null, "message": "Speech was detected but could not be transcribed. It may have been too quiet, too brief, or unclear. Ask the user to repeat, a little louder and closer to the microphone." }

Transcription and dependency failures return isError: true with the real cause (a missing model, a whisper load failure, Ollama not running, a timeout, or an empty model response), so a caller debugging can tell whether the failure was in capture, transcription, or the language model.

How It Works

mcp-listen uses decibri for cross-platform microphone capture. No ffmpeg, no SoX, no system audio tools required. Pre-built native binaries with zero setup.

Audio is captured as 16-bit PCM at 16kHz mono, the standard format for speech-to-text engines.

Silence-stopping uses the Silero voice activity detection model that ships inside decibri, running on-device through the bundled ONNX Runtime. Nothing extra is downloaded and no audio leaves the machine. The stop decision is measured in captured audio, not wall-clock time, and the VAD only decides when to stop: it never gates or alters the recorded samples.

The voice_query tool captures audio and transcribes it on this machine with whisper.cpp, sends the transcription to the local Ollama daemon, and returns the transcription and the response to the calling client. The audio stays on this machine.

Whisper Model Setup

The voice_query tool requires a Whisper GGML model file. Download one:

Linux / macOS:

mkdir -p ~/.mcp-listen/models

curl -L -o ~/.mcp-listen/models/ggml-base.en.bin https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-base.en.bin

Windows (PowerShell):

mkdir "$env:USERPROFILE\.mcp-listen\models" -Force

Invoke-WebRequest -Uri "https://huggingface.co/ggerganov/whisper.cpp/resolve/main/ggml-base.en.bin" -OutFile "$env:USERPROFILE\.mcp-listen\models\ggml-base.en.bin"

The model is ~150MB and downloads once. You can also set the WHISPER_MODEL_PATH environment variable to a custom directory.

Ollama Setup

  1. Install Ollama from https://ollama.com
  2. Pull a model: ollama pull llama3.2
  3. Ensure Ollama is running: ollama serve

Known Limitations

  1. A loud transient can register as speech. Silence-stopping decides "speech has started" from the VAD score, so a door slam or a cough can start the countdown and end the recording after silence_ms of quiet, yielding a short capture of mostly silence. The outcome is visible, not silent: the re

Only the beginning is shown; read the rest in the repo

Ask PopNx