New: Pepys Dictate is out. $9.99 once + tax

Pepys

Model Context Protocol

Pepys MCP Server

Yes, Pepys has an MCP server, listed in Claude's own Connectors Directory – search "Pepys" inside Claude to add it in one click. Connect any AI agent – Claude, Claude in Chrome, 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 an agentFull API docs

In Claude's Connectors Directory

Pepys is a listed connector in Claude's own Connectors Directory, not only an MCP server you configure by hand. The listing carries an automated Anthropic review, a fixed connector URL, and a published tool list, browsable from inside Claude itself.

Add it in Claude

Open Settings → Connectors → Browse connectors, search "Pepys," and add it – no URL to copy. Sign-in is OAuth against your own Pepys account, and usage bills to that account's credits, the same as connecting any other way. This also covers Claude in Chrome, which shares Claude's connector list with no extra setup.

Two other ways to connect

1. Hosted connector – no API key

Point a remote MCP connector at https://pepys.co/api/mcp directly, instead of going through the directory. The agent signs in to Pepys once (OAuth); transcription bills to your credits. This is the only route for ChatGPT, which has no connector directory yet: Settings → Connectors → Add custom connector (Claude has the same option too, for a direct URL instead of browsing).

2. Local server – your own key

Run the published pepys-mcp server 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.
  • list_transcriptions – List recent jobs so the agent can resume or re-export earlier work.
  • list_podcast_episodes – List a feed's episodes to pick exactly which one to transcribe.
  • 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.
  • ask_transcription – Ask a question about a transcript and get only citation-backed answers.
  • 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.

Example prompts

Once connected, try any of these directly in the agent's chat:

  • Transcribe https://youtube.com/watch?v=... with speaker labels and give me a summary.
  • Transcribe the latest 3 episodes of this podcast feed and tell me how much of my Pepys balance that used: https://feeds.example.com/show.rss
  • In my last transcription, find every place the speakers mention "pricing" and quote the exact timestamps.
  • Export my most recent transcript as an SRT file.

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.

Also published in

Beyond Claude's own directory (above), Pepys is published in the other registries 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, Claude in Chrome, 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.

Is Pepys listed in Claude's Connectors Directory?

Yes. Search "Pepys" in Claude's Settings → Connectors → Browse connectors and add it directly – no URL to copy. It's a Community-tier listing that has been through Anthropic's automated review, at claude.ai/directory/pepys-co.

How do I connect Claude or ChatGPT to Pepys?

In Claude, the fastest way is Settings → Connectors → Browse connectors, then search "Pepys." Otherwise, add a custom connector pointing at https://pepys.co/api/mcp (in Claude: Settings → Connectors → Add custom connector) – this is the only route for ChatGPT today. Claude in Chrome uses the same connector list, so it's available there too, automatically. 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.