mcp-youtube-channel-transcript-extractor
by mambalabsdev
README.md
# YouTube Channel Stats Extractor MCP Server
[](https://smithery.ai/servers/mambabuilt/mcp-youtube-channel-transcript-extractor) [](https://glama.ai/mcp/servers/mambalabsdev/mcp-youtube-channel-transcript-extractor) [](https://registry.modelcontextprotocol.io/v0/servers?search=com.mambabuilt/mcp-youtube-channel-transcript-extractor&limit=1) [](https://www.npmjs.com/package/@mambalabsdev/mcp-youtube-channel-transcript-extractor) [](https://www.npmjs.com/package/@mambalabsdev/mcp-youtube-channel-transcript-extractor) [](https://github.com/mambalabsdev/mcp-youtube-channel-transcript-extractor/blob/main/LICENSE)
<a href="https://mcprush.com/to/youtube-channel-transcript-extractor-mcp?ref=badge"><img width="380" height="200" src="https://mcprush.com/badge/youtube-channel-transcript-extractor-mcp/card.svg" alt="YouTube Channel Transcript Extractor MCP server" /></a>
MCP server for the Mamba Labs **YouTube Channel Stats Extractor** actor on Apify.
The npm package and the registry entry keep the name `mcp-youtube-channel-transcript-extractor`, so existing installs keep working; the product is YouTube Channel Stats Extractor.
Resolve a company domain or YouTube handle to the channel with subscriber count and channel metadata.
## What it does
Resolve a company domain, or a YouTube handle, to that company's YouTube channel. Returns the subscriber count, the stable UC channel id, channel name, creation date and description, as one flat Clay ready row. Subscriber counts are rounded by YouTube above roughly a thousand subscribers, on the page and in its official API alike, and the row flags that. Optional transcript pulling is available and is CURRENTLY GATED by YouTube: the caption track list is readable and the caption content endpoint returns an empty body without a proof of origin token, which the row reports as not_extractable rather than as a video having no captions. No API key needed. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
## Quick start
Add this to your MCP client configuration:
```json
{
"mcpServers": {
"mamba-youtube-channel-stats": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-youtube-channel-transcript-extractor"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
```
## Prerequisites
- Node.js 18 or newer
- An Apify API token from [console.apify.com/account/integrations](https://console.apify.com/account/integrations)
The actor is pay per event and consumes Apify credits per call. Pricing is on the
[actor page](https://apify.com/mambalabs/youtube-channel-transcript-extractor).
## Example prompts
- "How many YouTube subscribers does stripe.com have?"
- "Find the YouTube channel id for hubspot.com."
- "Does gitlab.com run a YouTube channel, and when was it created?"
## Tool and inputs
Tool: `get_youtube_channel_stats`
| Input | Type | Meaning |
|---|---|---|
| `company_domain` | string | Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to |
| `company_name` | string | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. |
| `handle` | string | Optional. A YouTube handle such as @shopify, or a full channel URL. Supplying it skips discovery and goes straight to the channel. |
| `includeFollowerCounts` | boolean | When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and need |
| `skipCache` | boolean | When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibi |
| `includeTranscripts` | boolean | When "true", full timestamped transcripts are pulled for the most recent videos on the channel and returned as one row per video. Default is "false" b |
| `transcriptVideoCount` | string | How many of the channel's most recent videos to pull transcripts for, when transcripts are on. Default 5. Each video is one extra fetch and one extra |
| `max_charge_usd` | number | Optional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged. |
## Reading the output
Every row carries a per platform `_status` field, and it is the field to read
first. The vocabulary is the same across the whole Mamba Labs social family:
| Status | Meaning |
|---|---|
| `ok` | fetched and parsed, the value is there |
| `not_found` | we looked and there is no such profile |
| `not_extractable` | the profile exists and the value is not on the wire to us |
| `blocked` | the platform refused us, worth retrying later |
| `identity_mismatch` | we found a real profile and it belongs to someone else |
| `skipped` | you did not ask for this platform |
**`false` and `null` are never interchangeable.** `false` means we looked and the
answer is no. `null` means we could not look. If you filter for companies with no
presence, filter on `false`, because `null` rows are unknown rather than absent.
## Pricing
You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:
| Event | Price per event (USD) | Fires when |
| --- | --- | --- |
| `apify-actor-start` | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
| `company-checked` | $0.0035 on the Free plan, down to $0.00245 on higher Apify plans | Once per company for which the discovery cascade completed and a non degraded channel row was produced, whether or not a channel was found. Does not fire on a degraded row. |
| `profile-resolved` | $0.0025 on the Free plan, down to $0.00175 on higher Apify plans | Once per company whose candidate channel URL passed the identity gate. Fires on the validation work, not on a populated subscriber cell. |
| `follower-count-extracted` | $0.0025 on the Free plan, down to $0.00175 on higher Apify plans | Once per channel where a numeric subscriber count was read off the public page. Does not fire when the owner has hidden the count, which reports not_extractable. |
| `transcript-extracted` | $0.015 on the Free plan, down to $0.0105 on higher Apify plans | Once per video for which transcript TEXT was actually returned. A video with no caption track does not charge, and neither does a video whose caption track exists but whose content YouTube refused to serve. Never fires when transcripts are turned off. This is deliberately strict: the fetch costs us roughly a cent whether or not it yields text, and the buyer should not carry that. |
The [actor's Apify page](https://apify.com/mambalabs/youtube-channel-transcript-extractor) carries the current prices. Running this server consumes Apify credits.
## Full actor documentation
[apify.com/mambalabs/youtube-channel-transcript-extractor](https://apify.com/mambalabs/youtube-channel-transcript-extractor)
## Mamba Labs GTM Suite
Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay
ready output convention, so their rows join on `company_domain` with no cleaning
step. Full fleet: [apify.com/mambalabs](https://apify.com/mambalabs)
## License
MIT
TDQS
A4.1/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool there is nothing to confuse it with, and the description clearly enumerates what it does (domain/handle → channel stats) and what it does not do (search, video listing, video detail). The only mild internal blur is that the tool name advertises transcripts while the body frames them as a gated option, but that is a scoping note, not a tool-selection ambiguity.
Naming Consistency5/5
The single tool follows a clean snake_case verb_noun pattern (get_youtube_channel_stats). No mixing of conventions or vague verb styles is present to break predictability.
Tool Count3/5
One tool is thin for a server that also implies transcript extraction and channel resolution; resolving, stats, and transcript pulling are collapsed into a single overloaded call. It is not mis-scoped enough to be wrong, but it sits at the borderline of too few.
Completeness3/5
Channel lookup and stats are covered, but the headline transcript capability is effectively unusable (caption content gated, reported as not_extractable), and there is no video listing, video detail, or multi-channel/batch operation. An agent can still retrieve channel stats, so gaps are notable rather than fatal.
Maintenance
ActivityMaintained
ResponsivenessNo issues