"Download this YouTube video for me" is one of the first things people ask their AI assistant — and the results vary wildly. Some assistants refuse outright. Some fetch metadata but fail to produce a file. A few actually return a downloadable video. This post tests all six major assistants on the same task and reports exactly what each can and cannot do as of June 2026.
I build TubePull, whose MCP server is one of the mechanisms several assistants use to complete the task — disclosed bias. The methodology and results are reproducible.
Methodology
- Prompt: "Download this YouTube video for me," followed by a single stable URL.
- URL: A public-domain clip from the NASA YouTube channel — NASA content is public domain under 17 U.S.C. § 105, making downloading uncontroversial. See our legality guide and public-domain archives post for the full picture.
- Account tiers: paid consumer tier where a paid tier gates the relevant feature.
- Date: June 2026, on the then-current model for each product.
- Success definition: an actual downloadable file or working signed link in the conversation — not a description, not a yt-dlp command, not metadata.
Where an assistant couldn't do it natively, I recorded whether a supported connector path exists — in 2026, the MCP connector is what actually decides the outcome.
Six assistants, six results
ChatGPT (Plus / Pro / Business) — works via MCP connector
Native: Refuses, citing YouTube's Terms of Service. With browsing: can fetch title and metadata, but not the file. The path that works: In late 2025 OpenAI shipped full remote MCP connector support in ChatGPT Developer Mode on Plus, Pro, Business, Enterprise, and Education accounts. Enable Developer Mode, add https://tubepull.com/mcp, and "download this YouTube video" returns a signed MP4 link. Verdict: works via MCP (Developer Mode required).
Claude (claude.ai web + Claude Desktop) — works via MCP connector
Native: Refuses. The path that works: Add https://tubepull.com/mcp as a custom connector on claude.ai web, ask in the conversation, receive a signed MP4 link. Tested on Claude.ai web (Sonnet 4.6) in June 2026 — four steps end to end. Full walkthrough: download YouTube videos with Claude guide. Verdict: works via MCP — the smoothest browser-based setup of the group.
Gemini (gemini.google.com + Gemini app) — does not work
Native: Refuses. Connector path: Gemini's consumer apps don't expose a remote-MCP custom-connector flow, so there's no supported way to wire in TubePull. Workaround: Gemini will write a yt-dlp script to run yourself, but that fails the test (no file in the conversation). Verdict: does not work. Gemini's strength is YouTube search and summarization — and Google has an obvious business reason not to ship one-click YouTube downloads into its own assistant.
Perplexity (web + Mac/Windows app) — works via MCP connector
Native: Refuses. The path that works: Settings → Connectors → add a custom connector with MCP server URL https://tubepull.com/mcp, then ask in the thread. The Mac app's connector behavior is often more reliable than the web tab. Full steps in our Perplexity MCP guide. Verdict: works via MCP.
Grok (grok.com / X) — does not work
Native: Grok is more permissive in tone than the others and will engage with the request, but it has no consumer-facing remote-MCP custom-connector flow as of June 2026, so it cannot actually fetch and return the file. Workaround: a developer can wire Grok's API up with custom tools, but that is a build project, not something a consumer user can do in the app. Verdict: does not work for end users.
Cursor (cursor.com) — works via MCP connector
This is the pleasant surprise. Cursor is a coding IDE, not a chat app, but it has had first-class MCP support for a while. Add TubePull as an MCP server in Cursor's settings — the config is plain JSON ({"mcpServers": {"tubepull": {"url": "https://tubepull.com/mcp"}}}) — ask in the chat pane, and you get the file. Verdict: works via MCP, and for developers it is arguably the cleanest setup because it is just a JSON entry. The MCP landing page lists Cursor among the supported clients.
What this means
As of June 2026, four assistants can download YouTube — Claude, Perplexity, ChatGPT, and Cursor — and all four use the same mechanism: a remote MCP connector. None does it natively; all refuse the bare request and only succeed once a connector is attached. The protocol is the gate, not the model.
Gemini and Grok are the holdouts. Google has a direct conflict of interest in shipping YouTube downloads into Gemini; Grok hasn't built a consumer remote-MCP connector flow yet. Both can discuss downloading or generate scripts, but neither completes the task in the conversation.
The bigger takeaway is trajectory. A year ago ChatGPT couldn't appear in the "works" column at all. OpenAI shipping full MCP connectors in late 2025 changed that. MCP is now an accepted open standard. It's reasonable to expect Gemini or Grok to add consumer connector support before this list is a year old — at which point the answer to "which AI can download YouTube" will simply be "whichever ones let you attach an MCP server."
Why none of them do it "natively" — and why that is fine
"Refuses natively" doesn't mean deliberately unhelpful. A language model has no built-in ability to fetch a media stream and hand you a file — that's an absent capability, not a policy decision. What assistants do have is a cautious posture toward platform Terms of Service, so they explain the caveat instead of pretending to do something they can't.
The connector model resolves both halves. The MCP server has the capability; attaching it is an explicit, user-initiated choice that puts responsibility for what you download on you. The model supplies intent and language understanding; the connector supplies the action. Neither is doing anything shady.
This also explains why "native YouTube download" is unlikely to ship in a major assistant. The legal complexity of baking it directly into the product is high; exposing a connector framework and letting users attach the tool of their choice is low-risk. The connector path is not a workaround — it is the design these products are converging on.
Comparison table
| Assistant | Native works | MCP connector support | TubePull MCP works | Free tier compatible | Setup time |
|---|---|---|---|---|---|
| ChatGPT | No | Yes (Developer Mode, paid tiers) | Yes | Paid tiers only | ~5 min |
| Claude | No | Yes (claude.ai web + Desktop) | Yes | Yes (free 3/day) | ~3 min |
| Gemini | No | No consumer flow | No | — | — |
| Perplexity | No | Yes (custom connector) | Yes | Yes (free 3/day) | ~4 min |
| Grok | No | No consumer flow | No | — | — |
| Cursor | No | Yes (JSON config) | Yes | Yes (free 3/day) | ~2 min |
The bottom line
If you want your AI assistant to hand you a YouTube file, the real choice is which connector-capable assistant you already use. Claude, Perplexity, ChatGPT, and Cursor all work today via MCP; the easiest free starting point is Claude or Perplexity with TubePull's free 3-per-day tier. Gemini and Grok can't do it yet, but the standard is spreading. For the deeper comparison, see our best hosted MCP server for YouTube guide.
TubePull Pro is intended for normal personal use — not mass downloading, automated scripts, or integrating TubePull into another service. See Section 7 of TubePull's Terms.
Related reading
- How to Download YouTube Videos with Claude — No Install Required
- Download YouTube Videos in Perplexity with MCP
- The Best Hosted MCP Server for YouTube
- Is SSSTik Safe? The $9.99/Week 'Free Trial' Trap Explained (2026)
- Ytmp3.cc and Y2meta Alternatives — 6 Safer YouTube to MP3 Tools (2026)
- Best Free YouTube Downloader in 2026 — We Tested 10 Tools
- The YouTube Downloader With No Ads (And Why Most Sites Are Full of Them)