Model Context Protocol
Pepys MCP Server
Yes, Pepys has an MCP server. Connect any AI agent – Claude, ChatGPT, Cursor, or any Model Context Protocol client – to https://pepys.co/api/mcp and it transcribes audio, video, and whole podcast feeds on its own: speaker diarization, correctly-timed SRT and VTT, paste-a-link, and search across a transcript. Sign in once with OAuth – no API key.
Connect in one step
1. Hosted connector – no API key
Point a remote MCP connector at https://pepys.co/api/mcp. The agent signs in to Pepys once (OAuth); transcription bills to your credits. In Claude: Settings → Connectors → Add custom connector. Best for Claude and ChatGPT.
2. Local server – your own key
Run the published pepys-mcpserver with your API key – best for local dev agents. Add to your client's MCP config:
{
"mcpServers": {
"pepys": {
"command": "npx",
"args": ["-y", "pepys-mcp"],
"env": { "PEPYS_API_KEY": "pk_live_your_key" }
}
}
}Grab a key under Settings → API keys. The full REST API lives on the developer docs.
What the agent can do
Both connection methods expose the same tools:
transcribe– Transcribe a file, a direct link, or a pasted YouTube / podcast URL.upload_file– Hand the agent a local file to transcribe via a presigned upload.get_transcription– Read back the transcript, segments, summary, and speaker labels.export_transcript– Return correctly-timed SRT, VTT, or plain text.transcribe_podcast_feed– Fan a whole RSS or Apple Podcasts feed out into one transcript per episode.search_transcript– Find the moment a phrase was said inside a long transcript.get_credit_balance– Check remaining minutes before a large job.
99+ languages with automatic detection, translation with timestamps preserved, and files from short clips to hours-long recordings – the same engine behind pepys.co.
Pricing
Pay-once, usage-based: 1 credit = 1 minute, and credits never expire. The 60 free minutes from signup apply through the MCP too. See pricing – from $0.85/hr at volume, no subscription.
Find it in the registries
Pepys is published in the MCP directories agents and tooling browse:
Smithery, mcp.so, and the MCP Registry.
FAQ
Does Pepys have an MCP server?
Yes. Pepys runs a hosted MCP (Model Context Protocol) server at https://pepys.co/api/mcp. Connect any MCP client – Claude, ChatGPT, or Cursor – and it can transcribe audio, video, and podcasts directly, then read the transcript back. You can also run the pepys-mcp server locally with your own API key.
How do I connect Claude or ChatGPT to Pepys?
Add a custom connector pointing at https://pepys.co/api/mcp (in Claude: Settings → Connectors → Add custom connector). You sign in to Pepys once with OAuth – no API key to paste – and transcription bills to your Pepys credits.
Do I need an API key?
Not for the hosted connector – it uses OAuth sign-in. The local pepys-mcp server (for dev agents on your machine) uses a bearer API key from Settings → API keys instead.
What can an AI agent do with the Pepys MCP?
Transcribe a file or a pasted link, transcribe a whole podcast feed, get speaker diarization, export correctly-timed SRT or VTT, search across a transcript, and check the credit balance – all without leaving the agent.
What does it cost?
The 60 free minutes granted on signup apply through the MCP too. After that it is pay-once, usage-based (1 credit = 1 minute, credits never expire); diarization, whole-feed batch, and word-level export unlock with any one-time purchase.