Transcribe

so.transcribePublished by transcribe.soOfficial publisherv1.8.0Updated Oct 24, 2026

Transcribe audio and video into speaker-labelled transcripts, subtitles, clips, and cited Q&A.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Transcribe lets an assistant turn audio and video into speaker-labelled transcripts, subtitles, clips, and cited Q&A through a hosted remote endpoint.

What you can do
Transcribe is a hosted service exposed as a remote MCP endpoint. According to the registry description, it converts audio and video into transcripts with speaker labels, and also produces subtitles, clips, and cited question-and-answer output. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
When to use it
Worth adding when an assistant needs to work with recorded audio or video: producing readable transcripts, generating subtitles, cutting clips, or answering questions about media content with citations.
Requirements
A remote MCP connection to the provider's endpoint over streamable HTTP. Authentication is required: either OAuth sign-in (the default) or an API key supplied in the Authorization header. No local runtime, package, or environment variables are declared.
Before you install
The Authorization header carries a secret credential; keep it private and prefer OAuth sign-in where possible. Uploaded audio and video are sent to a third-party service, so consider whether the media contains confidential or personal content before processing it.

Installation

In SourceWeft

  1. Open Transcribe 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/so.transcribe%2Fmcp/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": {
    "transcribe": {
      "type": "http",
      "url": "https://transcribe.so/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

4
  1. v1.8.0LatestOct 20, 2026
  2. v1.7.0Oct 4, 2026
  3. v1.6.1Sep 17, 2026
  4. v1.6.0Sep 16, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Transcribe integrations