Slack MCP Server vs YouTube MCP Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Slack MCP Server MCP Servers	YouTube MCP Server MCP Servers
Tagline	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.	Model Context Protocol server that pulls YouTube subtitles into any MCP-capable LLM client.
Category	MCP Servers	MCP Servers
Pricing	Free· Free / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.	Free· Free and open source (MIT). You only pay for whatever LLM sits on the other end of the MCP connection (Claude Desktop, Claude API, or any other MCP-capable client).
Model	—	—
Editorial score	—	—
Use cases	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation	YouTube video summarisationTranscript extraction for note-takingTurning tutorial videos into written how-tosQuote and timestamp lookup across long talksNon-English caption translation via the LLMResearch on podcast and interview contentFeeding lecture transcripts into a study assistantReference implementation for building your own MCP server
Pros	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API	Truly minimal install: one npm package plus yt-dlp, one JSON entry in your MCP client, done in under two minutes No YouTube Data API key, no OAuth, no Google Cloud project, and no quota to burn through Works on any video yt-dlp can reach, including auto-generated captions and non-English tracks Runs entirely on your machine so transcripts never leave your box before the LLM sees them MIT-licensed reference implementation that is frequently forked as a starting point for other MCP servers Actively maintained by a well-known open-source developer (Anaïs Betts, author of mcp-installer)
Cons	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails	Only returns subtitles: no video download, no thumbnail, no channel or metadata queries, no search Requires yt-dlp installed and on PATH, which trips up users on locked-down corporate Windows machines Silently useless on videos that have no captions at all (rare, but happens on new uploads) yt-dlp itself is a moving target against YouTube's anti-bot measures, so occasional breakage until you update the binary No built-in rate limiting or caching, so summarising a 200-video playlist in a loop will get your IP throttled
Website	github.com	github.com

Pick Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Pick YouTube MCP Server if

✅ Truly minimal install: one npm package plus yt-dlp, one JSON entry in your MCP client, done in under two minutes
✅ No YouTube Data API key, no OAuth, no Google Cloud project, and no quota to burn through
✅ Works on any video yt-dlp can reach, including auto-generated captions and non-English tracks
✅ Runs entirely on your machine so transcripts never leave your box before the LLM sees them

Compare a different pair →