Log inSubmit server
OpenTranscribe MCP logo

OpenTranscribe MCP

Routes authorized audio to selectable speech-to-text providers and returns a shared transcript format through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install OpenTranscribe MCP

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "opentranscribe-mcp": {
      "command": "uvx",
      "args": [
        "open-transcribe-mcp"
      ],
      "env": {
        "OT_ENVIRONMENT": "YOUR_VALUE_HERE",
        "OT_HOST": "YOUR_VALUE_HERE",
        "OT_DEFAULT_PROVIDER": "YOUR_VALUE_HERE",
        "OT_DEFAULT_MODEL": "YOUR_VALUE_HERE",
        "OT_SECURITY__AUTH_MODE": "YOUR_VALUE_HERE",
        "OT_SECURITY__BEARER_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx open-transcribe-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 2d ago.

Overview

OpenTranscribe MCP routes authorized audio files or HTTPS URLs to Microsoft MAI, ElevenLabs Scribe, or Groq Whisper and returns a provider-independent transcript. Its Streamable HTTP endpoint exposes transcription, model discovery, cost estimation, chunk retrieval, and transcript deletion tools. Use it when recorder hardware or audio sources should remain separate from the speech-to-text provider and downstream workflow. Routing policies can select providers by quality, cost, or latency while capability requirements such as diarization and timestamps remain explicit.

Use cases

  • Transcribe recorder audio with a selectable provider
  • Route speech recognition by quality, cost, or latency
  • Normalize transcripts across Microsoft, ElevenLabs, and Groq
  • Retrieve or delete stored transcript chunks
  • Connect authorized HTTPS audio sources to MCP workflows

Key features

  • Provider-independent transcript schema
  • Microsoft MAI, ElevenLabs Scribe, and Groq Whisper adapters
  • Streamable HTTP MCP endpoint
  • Capability-aware routing and retries
  • Cost estimation and model discovery
  • SSRF controls and optional result retention

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

8/8 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · open-transcribe-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit6d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How OpenTranscribe MCP works

What OpenTranscribe MCP does

OpenTranscribe MCP provides a speech-to-text boundary between audio sources and downstream MCP clients. It accepts an audio file or authorized HTTPS URL, sends the audio to a configured transcription provider, and normalizes the result into one transcript shape. Supported adapters include Microsoft MAI-Transcribe-2, ElevenLabs Scribe v2, and Groq Whisper.

The design lets operators use audio from recorders, phones, wearables, or other authorized sources without tying later workflows to one transcription subscription. Provider selection can be explicit, or the server can choose using a routing policy for quality, cost, or latency. Requests may also require capabilities such as diarization, timestamps, or a transcript style; unsupported models are excluded rather than silently returning an unmet capability.

How it works

The hosted service exposes MCP Streamable HTTP at /mcp and operates statelessly. Clients authenticate with a bearer token or an external OIDC arrangement. Health and readiness probes are available at /healthz and /readyz.

Audio can be passed through as an HTTPS URL when a provider supports that path. Otherwise, OpenTranscribe MCP uses a bounded streaming proxy. The server includes capability negotiation, routing policies, retries, and observable fallback behavior. Transcript responses include metadata describing the capabilities applied by the selected model.

Optional result retention is disabled by default. When enabled, temporary results can use memory or S3-compatible storage, with support for TTL-oriented deployment configurations.

Setup and configuration

Run the application from source with Python 3.12 and uv, or use Docker. A typical source installation clones the repository, creates a private environment file, runs uv sync, and starts the process with uv run open-transcribe-mcp. The default local endpoint is http://localhost:8000/mcp.

Configuration supplies the selected provider, model, provider endpoint and credentials, plus MCP authentication settings. The example Microsoft configuration uses OT_DEFAULT_PROVIDER=microsoft, OT_DEFAULT_MODEL=MAI-Transcribe-2, a Microsoft endpoint and API key, bearer authentication, and a randomly generated bearer token. Groq, ElevenLabs, and multi-provider configurations use their corresponding provider settings. Unused settings should be omitted, and credential files should be protected from other users.

Docker images can receive configuration through an environment file and runtime environment variables. The image includes the S3 extra, but storage remains off until configured. A reference Terraform deployment targets Scaleway Serverless Containers with HTTPS ingress, health probes, and optional result storage.

On Linux, the optional OpenTranscribe Setup Debian package bundles the runtime and a native setup application. It runs the engine as a client-owned STDIO process and does not open a network socket.

Tools and capabilities

The MCP tool surface includes:

  • transcribe_audio for submitting audio and selecting providers, models, routing policies, and requested capabilities.
  • list_transcription_models for discovering configured models and their capabilities.
  • estimate_transcription_cost for estimating provider transcription costs.
  • get_transcript_chunk for retrieving part of a stored transcript.
  • delete_transcript for removing a stored transcript.

Operational controls include SSRF protections, signed-URL redaction, zero content logging, and cost and resource limits. Authentication, retention, and storage behavior can be configured for the deployment.

Limitations and notes

Only audio the operator is authorized to access should be submitted. OpenTranscribe MCP does not bypass recorder access controls or defeat hardware protections. A requested capability can narrow provider selection; for example, requiring diarization excludes models that cannot provide it. Result storage is opt-in, and remote deployments should use an HTTPS proxy or equivalent secure ingress.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about OpenTranscribe MCP

OpenTranscribe MCP is an MCP server that connects authorized audio files or HTTPS URLs to Microsoft MAI-Transcribe-2, ElevenLabs Scribe v2, and Groq Whisper. Its main tools transcribe audio, list models, estimate costs, retrieve transcript chunks, and delete transcripts while returning a shared transcript format.

Install it from source with Python 3.12 and uv, or run its Docker image. Clone the repository, configure provider credentials and MCP authentication in a private environment file, run `uv sync`, then start it with `uv run open-transcribe-mcp`.

OpenTranscribe MCP supports Microsoft MAI-Transcribe-2, ElevenLabs Scribe v2, and Groq Whisper adapters. You can choose a provider and model explicitly or use automatic routing with default, quality, cost, or latency policies.

Connect an MCP client to `http://localhost:8000/mcp` for a local source deployment and authenticate with the configured bearer token. Hosted deployments use the corresponding HTTPS MCP endpoint and may use bearer or external OIDC authentication.

Yes, it accepts authorized HTTPS audio URLs. The server passes URLs directly to a provider when supported and otherwise uses a bounded streaming proxy, with SSRF controls and signed-URL redaction.

Related MCP servers

All in Speech-to-Text All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenTranscribe MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/opentranscribe-mcp?style=directory)](https://allmcps.com/mcp/opentranscribe-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/opentranscribe-mcp"><img src="https://allmcps.com/api/badge/opentranscribe-mcp?style=directory" alt="OpenTranscribe MCP on AllMCPs" /></a>