MCP Server

Overview

The TranscriptMagic MCP server gives any MCP-compatible AI client a one-click set of tools to fetch video transcripts from YouTube, TikTok, Instagram, and Facebook — plus check credit balance and recall transcript history. It is a remote MCP server over Streamable HTTP with OAuth 2.1 authentication. There is no API key to copy — users sign in once with Google when they connect, and the AI client manages its own short-lived token.

Server URL

https://mcp.transcriptmagic.com/mcp

If you are building a service or batch pipeline (no AI client in the loop), the REST API is a better fit. Same backend, same credits.

When to use MCP vs. the REST API

Use MCP when	Use the REST API when
You’re inside a chat with Claude, ChatGPT, Cursor, or Claude Code	You’re writing a service, agent runtime, or batch job
You want zero glue code	You want a predictable JSON contract
Your users need transcripts ad-hoc, in plain English	You need per-line YouTube timestamps
You don’t want to manage API keys	You’re integrating into a non-AI product

Tools

The server exposes six tools.

Transcribe tools (1 credit each)

transcribe_youtube

Fetch the transcript of a public YouTube video given its URL.Input

url (string, required) — full YouTube URL. Accepts youtube.com/watch?v=…, youtu.be/…, youtube.com/shorts/…, and m.youtube.com mobile links.

Cost 1 credit per successful call.Notes Returns plain text. Per-line timestamps are available in the REST API response, not in the MCP text output.

transcribe_tiktok

Fetch the transcript of a public TikTok video.Input

url (string, required) — full tiktok.com/@user/video/… URL or vm.tiktok.com/… short link.

Cost 1 credit per successful call.

transcribe_instagram

Fetch the transcript of a public Instagram video.Input

url (string, required) — instagram.com/reel/…, instagram.com/p/…, or instagram.com/tv/….

Cost 1 credit per successful call.

transcribe_facebook

Fetch the transcript of a public Facebook video.Input

url (string, required) — facebook.com/watch?v=…, fb.watch/…, facebook.com/reel/…, or Live replay URL.

Cost 1 credit per successful call.

Utility tools (free)

get_credit_balance

Returns the signed-in user’s remaining transcript credits and current plan.Input none.Cost Free; does not consume credits.

list_recent_transcripts

Lists the user’s recently saved transcripts (most recent first). Useful when the AI wants to recall something the user already fetched.Input

limit (integer, 1–50, optional, default 10) — max number of transcripts to return.
platform (youtube | tiktok | instagram | facebook, optional) — filter to a single platform.

Cost Free; does not consume credits. Each item includes the video URL, platform, title, and a short text preview.

Setup by client

Claude Desktop
Claude.ai
ChatGPT
Cursor
Claude Code

Open Claude Desktop → Settings → Connectors.
Click Add custom connector.
Paste the server URL: https://mcp.transcriptmagic.com/mcp.
A browser tab opens — sign in with Google and click Approve.
The tools become available in every chat. Try: “Summarize this YouTube video: <url>”.

Open claude.ai/settings/connectors.
Click Add custom connector.
Paste the server URL: https://mcp.transcriptmagic.com/mcp.
Sign in with Google in the popup, then click Approve.

Open Settings → MCP → Add new MCP server and paste:

{
  "mcpServers": {
    "TranscriptMagic": {
      "url": "https://mcp.transcriptmagic.com/mcp"
    }
  }
}

In your terminal:

claude mcp add --transport http TranscriptMagic https://mcp.transcriptmagic.com/mcp

Claude Code will open a browser tab for OAuth the first time you use a tool.

You can also manage connections from the dashboard MCP page — view connected clients and revoke them.

Authentication

The server implements OAuth 2.1 (RFC 8414 + dynamic client registration). The flow looks like this:

The MCP client requests the server’s authorization metadata.
It registers itself dynamically and redirects the user to TranscriptMagic’s consent screen.
The user signs in with Google and approves access.
The server issues an access token scoped to the client; the user’s TranscriptMagic account, credits, and history are linked.

Tokens are short-lived; clients refresh them automatically. There is nothing for end users to copy or paste.

Errors

The MCP server returns errors as isError: true content blocks the AI can read directly. Common cases:

Out of credits — “Out of credits. Top up or upgrade at transcriptmagic.com/dashboard/account.”
Invalid URL — the URL didn’t match the platform’s expected format.
No transcript available — public video, but no spoken audio or captions.
Private / login-walled — the video can’t be fetched without sign-in.

The AI will typically retry or ask the user for a different URL on its own.

Pricing

Free credits are included on signup. After that, 1 credit per successful transcribe_* call. Utility tools (get_credit_balance, list_recent_transcripts) are free. See the pricing page for plan details.

REST API

Fully documented REST endpoints for non-MCP integrations.

Authentication

Bearer-token auth for the REST API (separate from MCP OAuth).

Errors

Status codes and retry strategy for the REST API.

Rate limits

60 req/min on the REST API. MCP is rate-limited only by your credit balance.

Get started

Concepts

MCP Server

Overview

Server URL

When to use MCP vs. the REST API

Tools

Transcribe tools (1 credit each)

Utility tools (free)

Setup by client

Authentication

Errors

Pricing

REST API

Authentication

Errors

Rate limits

Get started

MCP Server

Concepts

Documentation Index

​Overview

Server URL

​When to use MCP vs. the REST API

​Tools

​Transcribe tools (1 credit each)

​Utility tools (free)

​Setup by client

​Authentication

​Errors

​Pricing

​Related

REST API

Authentication

Errors

Rate limits

Overview

When to use MCP vs. the REST API

Tools

Transcribe tools (1 credit each)

Utility tools (free)

Setup by client

Authentication

Errors

Pricing

Related