Audio Transcription MCP
An MCP server for local audio and video transcription with local Whisper or the OpenAI transcription API.
Package and CLI name: audio-transcription-mcp.
Requirements
- Python 3.11+
ffmpegavailable onPATH- For local transcription: install the
localextra ofcykk-audio-transcriber - For OpenAI transcription: install the
apiextra and setOPENAI_API_KEY
Install ffmpeg separately if it is not already available on your PATH.
On Debian/Ubuntu, use sudo apt install ffmpeg; on macOS with Homebrew, use
brew install ffmpeg; on Windows, install an FFmpeg build and add its bin
directory to PATH.
Install from source
git clone https://github.com/cykk/audio-transcription-mcp.git
cd audio-transcription-mcp
pip install ".[local]"
To use the OpenAI transcription API instead:
pip install ".[api]"
Install from PyPI
After the package is published to PyPI, install it directly:
pip install "audio-transcription-mcp[local]"
For the OpenAI transcription API:
pip install "audio-transcription-mcp[api]"
Installing without an extra does not install either transcription backend. Local Whisper may download the selected model on first use and requires sufficient disk space and memory.
Run
audio-transcription-mcp
For backward compatibility, audiototext-mcp remains available as an alias.
The server uses MCP stdio transport. Configure the command in an MCP client such as Claude Desktop, Cursor, or another compatible host:
{
"mcpServers": {
"audio-transcription": {
"command": "audio-transcription-mcp"
}
}
}
Tool
transcribe_file accepts a local file_path and optional model, language, task, prompt, and api_key arguments. It returns JSON containing the detected language, full text, and timestamped segments.
The server reads local files, so only configure it in clients you trust. API keys should preferably be supplied through OPENAI_API_KEY rather than tool arguments.
With an API key, the selected audio is sent to the OpenAI API. Without one,
transcription runs locally using Whisper; the model may be downloaded on first use.
Verify
After adding the server to an MCP client, call transcribe_file with a readable local audio or video file path. A successful response contains the detected language, full transcript, and timestamped segments.
To verify the package before configuring an MCP client, run:
python -c "import asyncio; from audiototext_mcp.server import mcp; print([tool.name for tool in asyncio.run(mcp.list_tools())])"
The command should include transcribe_file. A real transcription also requires
an installed local Whisper extra or a valid OPENAI_API_KEY for the API extra.
Related Product
MP3ToText is a browser-based audio and video transcription product. This MCP server runs independently and does not use the MP3ToText service.
License
MIT
Metadata
Release files for audio-transcription-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| audio_transcription_mcp-0.1.0.tar.gz | 5.1 kB | With provenance | Details for audio_transcription_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| audio_transcription_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for audio_transcription_mcp-0.1.0-py3-none-any.whl |
Total release size: 10.4 kB
Release files / audio_transcription_mcp-0.1.0.tar.gz
| Download URL | audio_transcription_mcp-0.1.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3a9094493fc874c991799cb1f49a60f4413a5c019560049c2356f6c07583ec5
|
|
BLAKE2b-256 checksum How to use checksums |
606a8d8b14df6c7f0b562e3c53fa165040eeff2ce48ab4df6205ad60abd1f69a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / audio_transcription_mcp-0.1.0-py3-none-any.whl
| Download URL | audio_transcription_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52b9593df03915034830edba8eedc57a2cafd3683bbca1110b7c352e11660ecf
|
|
BLAKE2b-256 checksum How to use checksums |
c6e311030c44aa85639cb435d3ca56647871239d2a16f24056066e601f19c0c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for audio-transcription-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for audio_transcription_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.