Skip to main content
📖 The AI Tool Bible

Linear MCP Server vs YouTube MCP Server

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

 Linear MCP Server logo
Linear MCP Server
MCP Servers
YouTube MCP Server logo
YouTube MCP Server
MCP Servers
TaglineOpen-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)Model Context Protocol server that pulls YouTube subtitles into any MCP-capable LLM client.
CategoryMCP ServersMCP Servers
PricingFree· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.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
Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server
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
  • Open source (MIT) and small enough to read end-to-end in an afternoon
  • One-line install via Smithery or straight npx in Claude Desktop config
  • Covers the create / update / search / comment loop that 90% of ticket workflows need
  • Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)
  • Clear tool schemas make it a good reference implementation for building your own MCP servers
  • Uses Linear's official GraphQL API, so permissions and audit trails stay intact
  • 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
  • Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse
  • Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team
  • Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user
  • Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management
  • Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits
  • 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
Websitegithub.comgithub.com
Pick Linear MCP Server if
  • ✅ Open source (MIT) and small enough to read end-to-end in an afternoon
  • ✅ One-line install via Smithery or straight npx in Claude Desktop config
  • ✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
  • ✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)
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 →