Goose Listen
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Goose Listen inspect recordings/call.wav and summarize active segments"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Goose Listen
Goose Listen is a small, local-first MCP extension that turns a PCM WAV file into bounded audio observations an agent can reason about without uploading the recording or pretending to understand more than the signal supports.
The first working slice answers narrow questions:
When is the recording quiet or active?
Where might clipping have occurred?
What are the sample rate, channel count, duration, peak, and RMS level?
What uncertainty and privacy boundary should accompany those observations?
It deliberately does not transcribe speech, identify people, infer emotion, or call a remote model.
Why this fits Goose
Goose treats external capabilities as MCP extensions. Goose Listen is a command-based stdio MCP server, so it can be launched locally and used as one bounded observation tool. The event envelope is intentionally neutral enough to support future microphones, replay fixtures, and optional on-device processors without coupling the core to one model.
Related MCP server: voice-analysis-mcp
Run
Requires Node.js 20 or newer.
npm install
npm run buildLaunch it with the directory it is allowed to inspect:
GOOSE_LISTEN_ROOT=/path/to/approved/audio node dist/index.jsOn Windows PowerShell:
$env:GOOSE_LISTEN_ROOT = 'C:\path\to\approved\audio'
node dist/index.jsAdd it to Goose as a custom command-line extension using node as the command and the absolute dist/index.js path as its argument. Keep the transport as stdio.
Tool
inspect_wav
Inputs:
file: a relative path underGOOSE_LISTEN_ROOT, or an absolute path still contained by itwindow_ms: observation window from 50 to 2,000 ms; default 250activity_threshold: RMS threshold from 0 to 1; default 0.02
Output:
deterministic file metadata
overall RMS and peak
coalesced
quiet,active, andpossible_clippingsegmentsexplicit limitations and a no-retention statement
Verify
npm test
npm run check
npm run buildThe tests generate their own short WAV fixture, verify observations, reject a path outside the approved root, and reject a non-WAV payload.
Roadmap
A permission-scoped microphone adapter with an obvious recording indicator
Deterministic replay fixtures for agent evaluations
Optional, separately consented on-device speech-to-text processors
Cross-platform packaging and Goose recipes
Accessibility evaluation with users who benefit from hands-free workflows
License
MIT
Available Tools
1 toolinspect_wavInspect a local WAV recordingARead-onlyIdempotent
Read an authorized PCM WAV inside GOOSE_LISTEN_ROOT and return bounded quiet, active, and possible-clipping observations. No network use, transcription, identity inference, or retention.
Inputs: file (required), window_ms, activity_threshold.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool in the server, there is no possibility of confusion between tools. The single inspect_wav operation is clearly described with a specific, unique purpose.
The tool name inspect_wav follows a clear verb_noun pattern and is readable. However, a single tool provides too little evidence to fully assess naming consistency across a server.
A single tool is far too few for a typical server surface, making it feel more like a one-off utility than a coherent tool set. Even a focused audio inspection server would benefit from additional operations such as listing files or retrieving metadata.
The surface is severely incomplete: it offers only one analysis operation with no way to enumerate available WAV files, access file metadata, or handle broader workflows. Agents would hit dead ends and be forced to rely on external mechanisms for basic context.
Maintenance
Related MCP Connectors
Voice quality analysis: PVQA and AQuA MOS for WAV files, VoIP call analysis for PCAPs
Check voice recording levels locally and share approved results with your assistant. OAuth required.
Media intelligence analysis for audio, video, and images via the Echosaw MCP server.
Analyze consented voice recordings for wellbeing and communication coaching.
Related MCP Servers
- MIT
- AlicenseAqualityCmaintenanceProvides local audio analysis tools for LLMs, enabling transcription, conversation dynamics, prosody analysis, and visual inspection without API keys.8MIT
- AlicenseAqualityCmaintenanceProvides local-first audio/video analysis by downloading media, transcribing it, and returning structured labels for topics, sentiment, sensitivity flags, and a publish/review/block gate.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, CPU-only audio post-production through tools for denoising, LUFS loudness normalization, silence removal, format conversion, pitch shifting, and speed changes. Supports podcast and video platform loudness compliance workflows.MIT