Are you the author? Sign in to claim
MCP server that tracks favorite YouTube creators and reports new uploads (no API key needed)
An MCP server that tracks your favorite YouTube creators and tells you when they've posted something new — right from Claude.
You: Add MKBHD to my YouTube watchlist
Claude: Now watching "Marques Brownlee" (UCBJycsmduvYEL83R_U4JriQ).
Latest upload so far: "The Best Car I've Ever Driven: McLaren W1"
— future checks will only report videos newer than this.
You: Did any of my channels post something new?
Claude: Checked 3 channel(s), found 1 new video total.
Marques Brownlee: 1 new video
- "..." (2026-07-05) https://www.youtube.com/watch?v=...
No YouTube API key, no Google Cloud project, no quotas — it reads each channel's public RSS feed.
add_channel — start tracking a creator by channel ID, @handle, or channel URLremove_channel — stop tracking onelist_channels — see everything you're watchingcheck_new_videos — check one channel, or all of them, for uploads since the last checkget_latest_videos — browse any channel's recent uploads without touching tracking statewatchlist://channels resource exposing your current watchlist as JSON┌─────────────┐ stdio (JSON-RPC) ┌────────────────────┐ HTTPS ┌──────────────────────┐
│ Claude │ ───────────────────▶ │ youtube-watch-mcp │ ────────▶ │ YouTube (public) │
│ (MCP client) │ ◀─────────────────── │ (this server) │ ◀──────── │ RSS + channel pages │
└─────────────┘ └────────────────────┘ └──────────────────────┘
│
▼
data/watchlist.json
(local, persisted state)
Transport. The server communicates with its client (Claude Desktop, Claude Code, etc.) over stdio — the client spawns node dist/index.js as a subprocess and exchanges JSON-RPC messages over stdin/stdout. This is the standard local-server transport in MCP; nothing is exposed over the network.
Tools vs. resources. Each capability above (add_channel, check_new_videos, ...) is registered as an MCP tool — a function with a typed input schema (validated with zod) that the model can decide to call based on your request. watchlist://channels is registered as an MCP resource instead — a read-only piece of data a client can pull in as context without "calling" anything.
Resolving a channel with no API key (src/youtube.ts). When you pass a @handle or a channel URL, the server fetches that page's plain HTML and extracts the channel's real ID from it. This turned out to be less trivial than it sounds: a channel page's HTML contains dozens of "channelId":"UC..." strings for unrelated channels (recommended/related-channel shelves), so grabbing the first match resolves to the wrong creator. Instead, the server reads the page's <link rel="canonical"> tag and "externalId" field — both of which specifically identify the page's own owner. If you pass a raw channel ID (UC...) directly, none of this scraping happens.
Fetching uploads (src/youtube.ts). Every YouTube channel exposes a public Atom feed at:
https://www.youtube.com/feeds/videos.xml?channel_id=UC...
No auth, no quota — but it only returns the ~15 most recent uploads. The server parses this XML with fast-xml-parser into a simple { channelTitle, videos[] } shape, where videos is ordered newest-first.
Tracking "new since last time" (src/index.ts, src/storage.ts). For each watched channel, the server persists the ID of the most recent video it has seen. check_new_videos walks the freshly-fetched feed from newest to oldest and collects every video until it hits that last-seen ID (or runs out of feed, if the channel posted more than ~15 videos since the last check). It then updates the stored ID to the current newest video. add_channel seeds this "last seen" value immediately with the channel's current latest upload, so adding a channel never immediately reports its entire back-catalog as "new."
Storage (src/storage.ts). The watchlist lives in data/watchlist.json, next to the compiled server — a flat JSON array of { channelId, nickname, addedAt, lastVideoId, lastCheckedAt }. No database; it's just read, mutated, and rewritten on every change.
git clone https://github.com/Achanandhi-M/youtube-watch-mcp.git
cd youtube-watch-mcp
npm install
npm run build
This compiles TypeScript from src/ into dist/.
claude mcp add youtube-watch -- node /absolute/path/to/youtube-watch-mcp/dist/index.js
Restart/reconnect Claude Code and the tools listed above become available.
Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS) under mcpServers, then restart the app:
{
"mcpServers": {
"youtube-watch": {
"command": "node",
"args": ["/absolute/path/to/youtube-watch-mcp/dist/index.js"]
}
}
}
@handle/URL scrapes public HTML rather than using an official API, so it could break if YouTube changes its page markup. Using a direct channel ID (UC...) with add_channel avoids this entirely.src/
index.ts MCP server: tool + resource definitions
youtube.ts Channel resolution + RSS feed fetching/parsing
storage.ts JSON-file watchlist persistence
data/
watchlist.json Your tracked channels (gitignored, created on first run)
MIT — see LICENSE.
Run Claude Code as an MCP server so any agent can delegate coding tasks to it
Browser automation using accessibility snapshots instead of screenshots
Google's universal MCP server supporting PostgreSQL, MySQL, MongoDB, Redis, and 10+ databases
Official GitHub integration for repos, issues, PRs, and CI/CD workflows