MCP Server

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

Local serverstdioGo

What is the MCP MCP server?

Give your AI agents the ability to listen. Microphone capture and speech-to-text. Exposed over MCP by the mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

The server ships on npm as mcp-listen, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • list_audio_devices — List available microphone input devices
  • capture_audio — Record audio from the microphone and save as WAV
  • voice_query — Capture, transcribe (whisper.cpp), and query a local LLM (Ollama)

Configuration

You will need one environment variable: WHISPER_MODEL_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

When to reach for it

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — list_audio_devices, capture_audio, voice_query — is a fair guide to whether it matches your workflow. It is maintained by analyticsinmotion; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
list_audio_devicesList available microphone input devices
capture_audioRecord audio from the microphone and save as WAV
voice_queryCapture, transcribe (whisper.cpp), and query a local LLM (Ollama)

How to install the MCP MCP server

{
  "mcpServers": {
    "listen": {
      "command": "npx",
      "args": ["-y", "mcp-listen"],
      "env": {
        "WHISPER_MODEL_PATH": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

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

VariableDescriptionRequired
WHISPER_MODEL_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use MCP to list audio devices.
  • Use MCP to capture audio.
  • Use MCP to voice query.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (list_audio_devices, capture_audio, voice_query) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.