gradio-transcript-mcp: A Gradio MCP Server for Audio/Video Transcription from URLs

Created By
bsmnyka year ago
Gradio demo cum MCP server to generate transcripts from Audio/Video
Overview

What is gradio-transcript-mcp?

gradio-transcript-mcp is a Gradio application that serves as an MCP (Model Control Protocol) server designed to transcribe audio and video content from URLs into text using OpenAI's Whisper and ffmpeg.

How to use gradio-transcript-mcp?

To use the application, clone the repository, install the dependencies, and run the Gradio app with python app.py. This will start the MCP server, allowing you to transcribe audio/video from URLs.

Key features of gradio-transcript-mcp?

  • Transcribes audio and video from URLs into text.
  • Supports format conversion to WAV.
  • Dynamic device selection (CPU or GPU) for processing.
  • Exposes a transcribe_url function for MCP clients.

Use cases of gradio-transcript-mcp?

  1. Transcribing lectures or meetings recorded as audio/video.
  2. Converting online video content into text for accessibility.
  3. Assisting content creators in generating transcripts for their media.

FAQ from gradio-transcript-mcp?

  • Can I use this for any URL?

    Yes, as long as the URL points to a valid audio or video file.

  • Is there a limit to the length of the audio/video?

    The length may depend on the processing capabilities of your machine and the configuration of the MCP client.

  • Is it free to use?

    Yes, the application is open-source and free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bsmnyk
Star
0
Language
Python
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago