Integrations

yt-text is a local stdio MCP server. Every client in this docs set is wiring the same underlying binary and exposing the same three tools:

  • get_transcript
  • list_languages
  • get_metadata

This section is intentionally narrow: it covers client configuration shape, config-file location, and setup verification. Tool ordering, fallback rules, and transcript interpretation are documented in the Agent Guide so the client-specific pages do not repeat behavioral guidance.

Common Setup Rules

Before editing any client config:

  1. Install yt-text and verify the binary:

sh yt-text --version

  1. If the binary is not on PATH, use an absolute path in the client config.
  2. Prefer a project-scoped config when you want teammates to share the same MCP setup.
  3. Restart the client after changing MCP configuration unless the client explicitly reloads MCP servers automatically.

Quick sanity check after setup:

  • ask the client to list available tools from yt-text
  • run get_metadata against a public YouTube URL

After the client is connected, use the Agent Guide for recommended in-session tool order and failure handling.

Integration Guides

Verification Date

The client-specific setup details in this section were checked against official product docs on 2026-04-16. These surfaces move quickly, so treat the linked official docs in each guide as the source of truth if a client UI changes.