Skip to main content
Glama

TubeScout 🔭

Turn YouTube into a research engine for your AI agent. An MCP server (no API key) plus a skill pack that make Claude Code, Codex, and OpenCode search YouTube like a database, read transcripts at scale, and mine videos for evidence — claims, numbers, demand signals — instead of vibes.

Idea-engine tools scan Reddit and forums. YouTube is where founders show receipts — revenue dashboards, playbooks, real numbers on camera — and nothing mines it. TubeScout does.

Quickstart (60 seconds)

Claude Code

claude mcp add --scope user tubescout -- npx -y tubescout

Codex

codex mcp add tubescout -- npx -y tubescout

OpenCode — add to ~/.config/opencode/opencode.json under "mcp":

"tubescout": { "type": "local", "command": ["npx", "-y", "tubescout"], "enabled": true }

That's it — no API key, no config. Then ask your agent things like:

"Find the 5 most-viewed videos about n8n from the last month and summarize what people are struggling with."

Easiest all-in-one (Claude Code): install as a plugin — MCP server + all 6 skills in two commands:

/plugin marketplace add not0lucky/tubescout
/plugin install tubescout@tubescout

Or install the skill pack manually (works for Claude Code, Codex, and OpenCode):

git clone https://github.com/not0lucky/tubescout && cd tubescout
./scripts/install-skills.sh   # installs into ~/.claude/skills, ~/.codex/skills, ~/.config/opencode/skills

Related MCP server: youtube-mcp

Tools

Tool

What it does

search_videos

Search with filters (upload window, duration, sort by views/date)

get_video

Full metadata + engagement (likesPer1kViews resonance signal)

get_transcript

Plain-text transcript via a resilient 3-strategy fallback chain

get_transcripts

Batch transcripts (up to 10 videos), per-video error tolerant

get_channel_videos

Channel positioning + recent uploads with view counts

get_search_suggestions

YouTube autocomplete = real search demand for keyword research

Skills (the research methods)

Skill

Use it to

/yt-breakdown <urls>

Skeptic's analysis of videos: extract every claim and number, stress-test for incentives, survivorship bias, verifiability

/yt-idea-mine <niche>

Mine a niche for product ideas backed by demand signals + pains real builders describe on camera

/yt-validate <idea>

Go/no-go verdict: demand, saturation, what competitors' numbers actually show

/yt-channel-intel <channel>

Read a channel's strategy: cadence, outliers, what performs vs what they publish

/yt-playbook <tutorial url>

Turn a tutorial into executable steps — exact commands, settings, and the gotchas said in passing — adapted to your stack

/yt-gap <niche>

Find demand-vs-supply gaps: heavily searched topics served by weak, old, or misfit videos — for content plans or product angles

All skills are context-aware: they read the conversation for what you're building, your stack, and videos already analyzed, and tailor verdicts to your actual leverage instead of giving generic advice.

See a real /yt-breakdown run on three "how I make $X/month" videos — including what survived the skeptic pass and what didn't.

How it works (honestly)

There's no magic here, and that's the point:

  • youtubei.js talks to YouTube's internal InnerTube API — the same one the site uses. No key, no quota.

  • Transcripts are YouTube's own captions, fetched through a fallback chain: the ANDROID-client timedtext track → the InnerTube transcript endpoint (known to 400 intermittently — retried with backoff) → local yt-dlp if you have it. Each response tells you which source served it.

  • All analysis happens in your agent. The server ships data; the skills ship method.

Limitations

  • Run it locally. YouTube aggressively rate-limits datacenter IPs — this is a local stdio server by design, not a hosted service.

  • YouTube changes internals without notice; when it breaks, update (npx always pulls latest) and file an issue with the failing video ID.

  • Videos with captions disabled can't be transcribed (rare; the error says so explicitly).

  • Caption scraping lives in YouTube ToS gray area — fine for local research tooling, don't build a hosted paid product on it.

Development

npm install && npm run build
npm test          # unit tests (offline)
npm run test:live # live smoke tests against real videos — run before publishing
npm run inspect   # MCP Inspector against the built server

MIT — see LICENSE.


Built by Anir — I automate things. More at agramprojects.com.

Available Tools

6 tools
get_channel_videosScan a channelA

Channel metadata (name, subscribers, description) plus its recent uploads with views — enough to read a channel's strategy, cadence, and what performs.

Inputs: channel (required), maxVideos.

get_search_suggestionsGet YouTube search suggestionsA

YouTube's autocomplete for a seed term — a direct read on real search demand. Use for keyword research: seed a niche term, get what people actually type. Chain suggestions of suggestions to map a topic space.

Inputs: query (required).

get_transcriptGet video transcriptA

Fetch a video's transcript as clean plain text. Resilient: tries InnerTube, then the timedtext caption track, then local yt-dlp if installed. Long transcripts are chunked — check totalChars and call again with offsetChars to continue.

Inputs: video (required), language, maxChars, offsetChars.

get_transcriptsGet transcripts for multiple videosA

Batch transcript fetch (max 10 videos, 3 at a time). Per-video failures don't kill the batch — failed entries carry an error field. Each transcript is truncated to fit; use get_transcript with offsetChars for full text of long ones.

Inputs: videos (required), language.

get_videoGet video intelA

Full metadata + engagement for one video: title, channel, publish date, views, likes, likesPer1kViews (resonance signal, typical range 10-50), category, keywords, description, hasCaptions.

Inputs: video (required).

search_videosSearch YouTube videosA

Search YouTube for videos (no API key). Returns id, title, channel, published, views, duration, snippet per hit. Use filters to narrow: uploadDate for recency, sortBy view_count to find what performs.

Inputs: query (required), sortBy, duration, maxResults, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: search, video metadata, single transcript, batch transcript, channel details, and search suggestions. There is no functional overlap that would confuse an agent.

    Naming Consistency5/5

    All tools follow a consistent action_noun pattern (search_videos, get_video, get_transcript, get_transcripts, get_channel_videos, get_search_suggestions). The pluralization for batch operations is intuitive and predictable.

    Tool Count5/5

    Six tools is a well-scoped size for a YouTube research server. Each tool adds a distinct capability without redundancy or bloat.

    Completeness4/5

    The surface covers the core YouTube research workflow: search, video details, transcripts, channel overview, and keyword discovery. Minor gaps like full channel video listing or comments are absent but not critical for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers