MCP Transcribe vs Pepys MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Transcribe vs Pepys MCP
In-depth architectural comparison of the MCP Transcribe and Pepys MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Transcribe
Speech-to-Text · Local stdio
Quality: 43/100 (Fair) | Auth: API Key required
Pepys MCP
Speech-to-Text · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
Verdict Summary: Choose MCP Transcribe if you need specialized Speech-to-Text tools running via a local process. Choose Pepys MCP if your workspace requires Speech-to-Text integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Transcribe when:
You need dedicated capabilities in the Speech-to-Text domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MCP_INTEGRATION_URL.
Primary tools included: Fast, lightweight transcription with no special ASR setup, Supports 100+ languages and noisy audio, Word-level timestamps and speaker separation.
This service provides fast and reliable transcriptions for audio/video files and voice memos. It allows LLMs to interact with the text content of audio/video file.
Pay-once transcription for audio, video, and whole podcast feeds via Pepys. Transcribe a file or a pasted YouTube/podcast link, get speaker diarization, export SRT/VTT, search a transcript, and check credit balance. Hosted connector (OAuth, no API key) or npx pepys-mcp. 99+ languages.
Category & Scope
Tools & Capabilities Breakdown
MCP Transcribe Tools (6)
Fast, lightweight transcription with no special ASR setup
Supports 100+ languages and noisy audio
Word-level timestamps and speaker separation
Accepts local file paths or public URLs
Collaboration support via Transcribe.com teams
Account balance and transcription management tools
Pepys MCP Tools (9)
transcribe
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Transcribe is categorized under Speech-to-Text and uses a local stdio subprocess. In contrast, Pepys MCP belongs to Speech-to-Text using local stdio subprocess. Select MCP Transcribe when you need capabilities focused on speech-to-text and Pepys MCP when you require tools for speech-to-text.
Transcribe hours-long audio or video into an accurate, speaker-labeled (diarized), timestamped transcript with correctly-timed SRT/VTT captions – work a general model can't do on a raw file. Accepts a file_ref from upload_file or a url (YouTube, podcast episode, RSS feed, Google Drive/Dropbox share). Audio is never used to train models. Returns { job_id, status }; fetch the result with get_transcription.
get_transcription
Fetch a transcription by job_id: full text, per-speaker timestamped segments, summary, duration_seconds, billed_minutes, and language. Set wait_ms (up to 25000) to long-poll so short clips come back in one call; otherwise poll until status is 'done'.
upload_file
Upload local audio/video the agent is holding (as base64 bytes or a file path) and get back a file_ref to pass to transcribe. Use this when the media has no public URL. Requires the Pepys R2 storage backend.
list_transcriptions
List this account's recent transcription jobs with their job_id, status, title, and duration, so you can resume, fetch, or export an earlier result instead of re-transcribing.
list_podcast_episodes
Given a podcast RSS feed or Apple Podcasts show URL, list its episodes (title, publish date, episode_guid, audio_url) so you can pick exactly which one to transcribe.
transcribe_podcast_feed
Batch-transcribe a whole podcast feed in one call – fan out every episode, or the latest N, to individual jobs. Returns a set of job_ids. Paid capability (throughput/abuse gate).
export_transcript
Export a finished transcript as SRT, VTT, TXT, Markdown, or JSON, with correct caption timings. Segment-level export is free; word-level-timed export (word_level:true) is a paid unlock. (DOCX/PDF are available in the Pepys web app.)
search_transcript
Search inside a long transcript for a phrase and get back only the matching timestamped segments – locate a quote or topic in an hours-long recording without loading the whole transcript into context.
get_credit_balance
Return the account's remaining transcription credits (in minutes) so you can check headroom before starting a large batch and avoid running out mid-run.