SHOW_USAGELABSCO SUMMARY
The mount is the boundary.
The server only sees the directory you bind in, which makes the blast radius of handing an assistant your microphone recordings a decision you make in the config rather than a matter of trust. The one thing to be deliberate about is cost: starting a job consumes your mocoVoice allowance, so the file listing and format check are worth running before the job, not after a failed one.
What it is
An MCP server that connects a client to mocoVoice for transcription. It works over a directory you mount, so the assistant can see which media files are available, start a job on one, and fetch the transcript when it is done.
What you get
- A list of the audio and video files it can actually reach, limited to the directory you mounted —
SHOW_AVAILABLE_FILES - The audio and video formats it accepts, before you convert anything —
SHOW_AVAILABLE_FORMATS - Transcription job submission against a file, given as an absolute path —
START_TRANSCRIPTION_JOB - Result retrieval by transcription id, and a list of every past transcription with its status —
SHOW_TRANSCRIPTION_RESULT,CHECK_TRANSCRIPTION_STATUSES - A capability listing of the server itself —
SHOW_USAGE - Uploads of up to 5GB, covering .wav, .mp3, .m4a, .caf, .aiff, .wma, .flac, .ogg and .aac for audio and .avi, .mp4, .rmvb, .flv, .mov and .wm for video
Requirements
A mocoVoice API key with READ and WRITE permissions, as MOCOVOICE_API_KEY, plus MOCOVOICE_API_URL pointing at https://api.mocomoco.ai/api/v1. Docker, since the documented setup runs ghcr.io/mocomoco-inc/mocovoice-mcp-server with your media directory bind-mounted to /workspace — files are addressed by absolute path. Transcription is billed as mocoVoice API usage, and starting a job consumes quota. The package is moco-voice-mcp (version 0.1.0); it is offered as a beta.
Setup effort
Run a container — pull the image and point your client at it
USE CASES
01
Transcribing a meeting recording
List what is in the mounted folder, start the job on the right file, then read the transcript back when it completes.
02
Checking a file will be accepted before spending quota
Read the supported format list and confirm the file is one of them, rather than discovering it in a failed job.
03
Catching up on jobs you started earlier
List past transcriptions with their statuses and pull the results of the ones that have finished.
6 tools
Listed in project docs. Your client may show a different list.
SHOW_AVAILABLE_FORMATSSHOW_AVAILABLE_FILESSTART_TRANSCRIPTION_JOBSHOW_TRANSCRIPTION_RESULTCHECK_TRANSCRIPTION_STATUSESBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
MOCOVOICE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mocoVoice MCP Server": {
"command": "docker",
"args": [
"run",
"--pull",
"always",
"-i",
"--rm",
"--mount",
"type=bind,src=<YOUR_DIR_PATH>,dst=/workspace",
"-e",
"MOCOVOICE_API_KEY",
"-e",
"MOCOVOICE_API_URL",
"ghcr.io/mocomoco-inc/mocovoice-mcp-server"
],
"env": {
"MOCOVOICE_API_KEY": "<YOUR_API_KEY>",
"MOCOVOICE_API_URL": "https://api.mocomoco.ai/api/v1"
}
}
}
}
