API archive entry · source-reported

Transcript Dock

Transcripts of YouTube, TikTok and Instagram videos in one tool call, with SRT and VTT exports

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

An MCP server that wraps the TranscriptDock public API, so Claude, Cursor and other agents can submit transcription jobs and read back transcripts without you leaving the chat. It only calls the public /v1 API (API reference). The hosted server signs you in with OAuth; the local one needs a TranscriptDock API key (tdlive...). The hosted server is https://www.transcriptdock.com/mcp (Streamable HTTP). Use that exact URL: the apex domain redirects, and clients drop the Authorization header on a cross origin redirect. Open Customize, Connectors, choose Add custom connector, and paste https://www.transcriptdock.com/mcp. Choose Add, then Connect, sign in to TranscriptDock and allow access. No API key needed: the server publishes RFC 9728 metadata and signs people in through OAuth 2.1 (dynamic client registration, S256 PKCE). An OAuth connection can read and submit jobs and read transcripts, nothing else. Then run /mcp and choose Authenticate. To use an API key instead, send it…

TranscriptDock/transcriptdock-mcp on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-11-11T17:00:56.430Z

Inside the original README — Document outline
  1. TranscriptDock MCP server
  2. Remote (no install)
  3. Claude (claude.ai, Desktop, mobile)
  4. Claude Code and other clients
  5. Install locally (npx)
  6. Claude Desktop (stdio)
  7. Claude Code
  8. Cursor
  9. Sources and modes
  10. Configuration
  11. Tools
  12. Development

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Nov 11, 2026
  2. Last directory-field change: Nov 11, 2026
  3. Current source observation: Nov 13, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.