Pepys Mcp

co.pepysPublished by pepys.coOfficial publisherv0.1.1Updated Oct 24, 2026

Transcribe audio & video: diarization, timed SRT/VTT, podcasts, paste-a-link, whole-feed batch.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Lets an assistant transcribe audio and video with speaker diarization and timed SRT/VTT output, including podcasts and whole-feed batches.

What you can do
Pepys provides transcription of audio and video through an assistant. It supports speaker diarization, timed subtitle output in SRT or VTT, podcast transcription, transcription from a pasted link, and batch processing of an entire feed.
When to use it
Useful when you want an assistant to turn recordings, podcasts, or linked media into text or subtitles, especially when speaker labels or timed captions are needed, or when processing many episodes from a feed at once.
Requirements
A remote endpoint at pepys.co or the local npm package pepys-mcp over stdio. OAuth authentication is required, and a Pepys API key supplied through the PEPYS_API_KEY environment variable.
Before you install
Requires a live API key (PEPYS_API_KEY) that should be kept secret. Submitted audio and video, including pasted links and feed content, are sent to a third-party service for processing.

Installation

In SourceWeft

  1. Open Pepys Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.pepys%2Fpepys-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pepys": {
      "type": "http",
      "url": "https://pepys.co/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.