Transcribe

com.transcribevideototextPublished by transcribevideototext.comOfficial publisherv1.0.0Updated Oct 25, 2026

Transcribe audio & video to text for AI agents: 100+ languages, speaker labels, webhooks.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant turn audio and video into text, with speaker labels and support for over 100 languages.

What you can do
Submit audio or video for speech-to-text transcription in more than 100 languages, with speaker labels separating who said what. Receive the resulting text for use in an assistant's answers or downstream work. Set up webhooks so transcription results are delivered when jobs finish.
When to use it
Useful when an assistant needs to work with spoken content — meeting recordings, interviews, podcasts or video — and needs a text version it can read, search or summarize.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. Sign-in through OAuth is required.
Before you install
Transcription sends your audio and video files to a third-party service, so consider whether the content is sensitive or confidential. Webhook delivery means results leave the service to an address you configure.

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/com.transcribevideototext%2Ftranscribe/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://mcp.transcribevideototext.com/mcp"
    }
  }
}

README

This repository has no README.

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. v1.0.0LatestSep 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.