Analyzes YouTube channels and videos to produce structured intelligence reports.
Accepts a YouTube channel URL, @handle, channel ID, or legacy URL, plus optional max_videos (default 5, max 50).
Fetches recent videos, extracts transcripts, and counts videos analyzed vs transcripts available.
Performs keyword frequency analysis across all transcripts to identify top topics.
If GEMINI_API_KEY is set, produces per-video semantic analysis with theme, named entities, and tags (topics_structured); otherwise falls back to keyword-only mode.
Returns a JSON report with channel metadata, sample video IDs, topics, analysis mode note, and optional output path to a local artifact file.
Requires YOUTUBE_API_KEY and APIFY_TOKEN; GEMINI_API_KEY is optional.
Extracts structured intelligence from YouTube channels, including transcript extraction, topic frequency analysis, competitive signal detection, and content positioning analysis.
MCP server for extracting structured intelligence from YouTube channels and videos.
Analyzes YouTube channels to produce structured intelligence reports:
Transcript extraction across recent videos (up to 50 videos)
Semantic topic extraction per video via Gemini (theme, named entities, tags)
Keyword frequency analysis across all transcripts (fallback when Gemini is unavailable)
Related MCP server: MCP YouTube Intelligence
You need API keys for three services:
Variable | Where to get it |
| Google Cloud Console → YouTube Data API v3 |
| Apify Console → Account → Integrations → API token |
| Google AI Studio → Get API key |
GEMINI_API_KEY is optional — if omitted, the tool falls back to word-frequency topic extraction instead of semantic analysis.
Optional
Variable | Default | Description |
|
| Directory where per-channel JSON analysis artifacts are written |
npm install -g mcp-youtube-intelligencemcp-youtube-intelligence --version # or -v — print the installed version and exit
mcp-youtube-intelligence --help # or -h — print usage and exitRunning the command with no flags starts the MCP server itself (stdio transport) — this is what an MCP client config invokes; it's not meant to be run bare in a terminal for interactive use.
Add to your Claude Desktop / MCP client config:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"youtube-intelligence": {
"command": "mcp-youtube-intelligence",
"env": {
"YOUTUBE_API_KEY": "your-youtube-api-key",
"APIFY_TOKEN": "your-apify-token",
"GEMINI_API_KEY": "your-gemini-api-key"
}
}
}
}analyze_channel — Extract intelligence from a YouTube channel
channel_url: YouTube channel URL or @handle. Accepts:
- @handle (e.g. @fireship)
- full URL with handle (e.g. youtube.com/@fireship)
- /channel/UC... URL
- bare 24-character UC... channel ID
- legacy /c/name or /user/name URL
max_videos: Number of recent videos to analyze (default: 5, max: 50)Example prompt: "Analyze the @fireship YouTube channel and tell me what topics they cover most."
npm install
npm run build
npm testMIT
Analyze a YouTube channel and return a JSON object with: channel_id, channel_title, channel_url, sample_video_ids[], videos_analyzed (count of videos fetched from playlist), transcripts_available (count with actual caption content), topics[] (top keyword frequencies across all transcripts), topics_structured[] (per-video semantic analysis — each entry has video_id/theme/entities[]/tags[]), note (which analysis mode ran), and optional output_path (local artifact path). Requires YOUTUBE_API_KEY and APIFY_TOKEN; set GEMINI_API_KEY for topics_structured semantic analysis (falls back to keyword-only when absent). Supported channel inputs: @handle (e.g. @fireship), youtube.com/@handle URL, /channel/UC... URL, bare 24-char UCxxxxxx ID, or legacy /c/ and /user/ URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| max_videos | No | Number of recent videos to analyze (default 5, max 50) | |
| channel_url | Yes | YouTube channel URL or @handle (e.g. @fireship, https://www.youtube.com/@fireship, UCxxxxxxx) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses output structure, dependencies, fallback mode, and input types. Missing details on rate limits or error handling, but still transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is verbose but every sentence adds useful information. It front-loads the output structure and maintains clarity. Could be slightly trimmed without losing value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description fully explains the return object. Covers inputs, dependencies, and analysis modes, making it complete for a tool with two parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, but description adds value by explaining accepted formats for channel_url and notes max_videos default/limit. Minor overlap with schema for max_videos.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: analyze a YouTube channel and return a JSON object with specific fields. It distinguishes the resource and action without ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context on when to use, including required API keys, fallback behavior, and supported input formats. However, it does not explicitly mention when not to use or alternatives, though no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.1.10analyze_channelScored across 1 tool
Only one tool exists, so there is no possibility of confusion with other tools.
The single tool name 'analyze_channel' follows a clear verb_noun pattern, making it predictable and unambiguous.
With only one tool for a domain like YouTube intelligence, the surface is too narrow; typical well-scoped servers have 3-15 tools.
The server only offers channel analysis, missing obvious operations like video search, video details, playlist management, and subscription handling, leaving significant gaps.
YouTube transcripts, search, channel browsing, and playlists for AI agents via MCP.
An MCP server that gives any LLM or agent clean YouTube transcripts on demand: a single video, a whole channel, or a playlist, plus AI cleanup of auto-generated captions. API-key auth, credit-based, same backend as the public v1 API. Get a free API key with 25 free credits at youtubetranscriptdownload.com/account.
YouTube data for AI agents: channels, videos, transcripts, comments, search. Video research.
Your agent needs to find video — which channels own a topic, which videos rank for a phrase, what exists in a given country and language. **What you can ask for** • "Which videos rank for 'rag pipeline tutorial' in the US this month?" • "Find channels publishing about MCP, sorted by relevance." • "What playlists cover this subject in Japanese?" • "Search videos uploaded this week only." **How to use it** Point any MCP client at https://mcp.aisa.one/youtube-search/mcp and sign in with OAuth — there is no key to create or paste. One search tool covering videos, channels and playlists, narrowed by country, language, upload date, duration and sort order. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the video here, then ask the same agent what the channel's site traffic is or what the same phrase does in Google — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/social/mcp for X plus Instagram, Reddit, Pinterest and YouTube; https://mcp.aisa.one/gtm/mcp for those plus Similarweb and Apollo.
