Local MCP server/Productivity

WhipScribe MCP server

Local MCP server

WhipScribe transcribes audio and video files, YouTube links, and podcast links in 99+ languages. Its tools are transcribe_url, transcribe_file, get_job_status, get_transcript, and list_recent_jobs; transcripts can be exported as TXT, SRT, VTT, or DOCX. The provider documents a local uvx stdio server with WHIPSCRIBE_API_KEY and WHIPSCRIBE_API_BASE=https://whipscribe.com/api/v1. It does not document a hosted /mcp endpoint, OAuth, or search and summarize tools.

API key (WHIPSCRIBE_API_KEY) Local install path Reviewed 2026-11-16
About

Where it fits

Content teams, researchers, and creators who need multilingual transcription and transcript exports.

  • Transcribe a YouTube or podcast link.
  • Fetch a transcript as SRT, VTT, or DOCX.
  • Check job status or list recent jobs.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio server

Set WHIPSCRIBE_API_KEY and WHIPSCRIBE_API_BASE=https://whipscribe.com/api/v1 before starting the server. The README documents local stdio, not a hosted /mcp endpoint or OAuth.

  1. Install uv

    The provider documents running the package with uvx.

  2. Set credentials

    Export WHIPSCRIBE_API_KEY and WHIPSCRIBE_API_BASE=https://whipscribe.com/api/v1.

  3. Run the server

    Register the stdio command in your MCP client.

    uvx whipscribe-mcp

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

WhipScribe repositoryhttps://github.com/neugence/whipscribe-mcp