YouTube MCP Server for Transcript Workflows

Use Scority transcript data in MCP-style workflows. The Transcript API supplies the text and timestamped segments that local tools and agents need.

View MCP docs View API docs

Give an agent one transcript action.

A useful MCP-style workflow needs a protected way to fetch transcript text and timed segments by video URL or video ID. Scority supplies that transcript contract through the HTTP API and OpenAPI spec.

Tool

get_youtube_transcript

Fetch transcript text and timed segments for many public YouTube videos with accessible captions.

Auth

Environment key

The MCP process reads SCORITY_API_KEY from the local environment. Keys are not passed in tool arguments.

Output

Agent-friendly JSON

Returns text, language, source, segments, segment_count, and text_length without internal cache or proxy details.

Example tool call.

MCP clients can ask for a transcript by URL or video ID. Language selection uses the same language parameter as the Transcript API.

tool-call.json

{
  "tool": "get_youtube_transcript",
  "arguments": {
    "video_url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
    "language": "en"
  }
}

{
  "tool": "get_youtube_transcript",
  "arguments": {
    "video_url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
    "language": "en"
  }
}

tool-call.json7 lines

One transcript tool by design.

The current product surface is intentionally focused on transcript retrieval. Search, channel metadata, playlist traversal, upload processing, billing, and dashboard operations are separate product surfaces and are not part of this transcript workflow.

Use the HTTP API directly for production services.
Use the repository wrapper when you want a local stdio tool around the same endpoint.
Do not expose Scority API keys to browser clients or public prompts.
Some videos can still return transcript_not_available or upstream_transcript_failed.