# How do you connect YouTube to Claude so it can analyze any channel Claude has no official YouTube connector, but you can add one free in about two minutes via Composio MCP and let Claude analyze any channel. Source: https://xin-stasr.top/how-do-you-connect/ · based on the channel [Business Workflow](https://www.youtube.com/channel/UCmyGByNwuX8T-N1zZ8IkmDw) · Video: [Claude Can Now Analyze Any YouTube Channel (Free Setup)](https://www.youtube.com/watch?v=SLvZuDnAK0k) · 2026-10-31 ![How do you connect YouTube to Claude so it can analyze any channel](https://xin-stasr.top/how-do-you-connect/how-do-you-connect.webp) ## Key takeaways - Claude ships without an official YouTube connector, so the integration is added manually as a custom connector. - Composio provides the MCP endpoint connect.composio.dev/mcp, which is pasted into Claude's connector settings. - YouTube access is authorized inside Composio under Apps → YouTube → Connect using a Google sign-in. - The whole setup is free, requires no code, and takes roughly two minutes according to the source walkthrough. - Once linked, a single prompt such as "Analyze this YouTube channel for me" triggers the channel analysis. You connect YouTube to Claude by adding a custom MCP connector that points to Composio, then authorizing YouTube with your Google account inside Composio. Claude has no official YouTube connector, but the workaround is free, requires no code, and takes about two minutes: add the connector, paste the Composio MCP URL, sign in to YouTube, and ask Claude to analyze the channel. ## Why Claude needs a custom connector for YouTube Anthropic's Claude ships with a set of first-party connectors, and YouTube is not one of them, so the Connectors screen in Claude settings has nothing to click for video data. The gap is closed by the Model Context Protocol, or MCP, an open standard that lets Claude call external tools through a single URL. Instead of building an API integration yourself, you point Claude at an MCP server that already wraps the YouTube API and handles the authentication for you. Composio is the service used in the Business Workflow walkthrough, and it is the piece that makes the setup a two-minute job rather than a development project. It hosts an MCP endpoint at connect.composio.dev/mcp, manages the OAuth handshake with Google, and exposes YouTube as a set of callable actions. The practical result is that Claude stops guessing about a channel and starts reading real metadata: titles, descriptions, tags, view counts and publishing dates. ## Step-by-step setup in Claude The entire configuration happens in two browser tabs and follows five short moves. 1. Open Claude and go to **Connectors** in the settings. Confirm that no YouTube connector is listed; this is expected. 2. Choose to add a **custom connector** and give it a recognizable name, for example "YouTube via Composio". 3. Sign up free at Composio and copy the MCP server URL, `connect.composio.dev/mcp`, then paste it into the connector field in Claude and click **Continue**. 4. In Composio, open **Apps**, select **YouTube**, and click **Connect**. Sign in with the Google account that owns or manages the channels you want to work with. 5. Return to Claude and send a prompt such as "Analyze this YouTube channel for me", pasting the channel URL. No API keys are copied by hand and no code is written. The Google sign-in is the only place where credentials are entered, and it happens inside Composio rather than inside Claude. ## What Claude can actually do once YouTube is linked With the connector active, Claude can pull the public data behind a channel URL and reason over it, which turns it into a research assistant for content planning. Typical requests that work well include comparing a channel's top-performing videos against its recent uploads, summarizing what topics a competitor covers most often, extracting the title patterns behind high-view videos, and drafting a content calendar that fits an existing publishing rhythm. Because the analysis runs on real channel data rather than on Claude's memory, the output reflects what is actually published. That matters for niche research: you can ask for a breakdown of formats, video length trends, or the gap between a channel's most-viewed uploads and its average performance, and get numbers instead of impressions. It is equally useful for auditing your own channel before a rebrand or for preparing a pitch with evidence about a competitor's upload cadence. ## Practical limits and how to keep the connection healthy Access is tied to the Google account you authorize in Composio, so Claude sees the channels that account can reach and nothing beyond that. Public channel data is the normal working scope; private analytics such as watch time, impressions and subscriber demographics are not part of the standard YouTube data surface exposed this way. Treat the connector as a research and planning tool, not as a replacement for YouTube Studio. Two habits prevent most failures. First, if Claude reports that it cannot reach YouTube, reopen Composio, check that the YouTube app still shows as connected, and reconnect if the token has lapsed. Second, keep prompts specific: naming the channel URL and the exact question produces far better results than a vague request to "look at my channel". Disconnecting is equally simple, since removing the custom connector in Claude or revoking the app in Composio cuts access immediately. ## Who this setup is for Creators, social media managers and agencies get the most value, because the workflow replaces manual spreadsheet research with a conversation. A manager juggling several client channels can keep the connector in place and switch context by pasting a different channel URL, while a solo creator can use it to spot which topics deserve a follow-up video. The no-code requirement means the setup is open to people who have never touched an API console. The same MCP pattern extends beyond YouTube: once you understand that a custom connector is just a URL plus an authorization step, adding other apps that Composio supports follows the same logic. That makes this a small but reusable skill for anyone building an AI-assisted content workflow. ## Summary Connecting YouTube to Claude is a five-step, no-code process built on a custom MCP connector pointed at Composio's endpoint, followed by a Google sign-in for YouTube inside Composio. Once linked, Claude can analyze channel data on demand and support content planning with real numbers rather than assumptions. The setup is free and reversible, and the main maintenance task is checking that the YouTube app stays connected in Composio. The walkthrough above comes from the Business Workflow channel, which publishes AI automation tutorials of this kind. ## Questions & answers **Does Claude have an official YouTube connector?** No. Claude's built-in connector list does not include YouTube, which is why the setup relies on a custom MCP connector. You add the Composio endpoint manually, then authorize YouTube with Google inside Composio. **Is connecting YouTube to Claude free?** Yes. Composio offers a free sign-up for the MCP endpoint, and Claude accepts custom connectors without an extra purchase. The only cost involved is whatever Claude plan you already use. **What data can Claude see after YouTube is connected?** Claude can read the public data behind a channel URL, such as video titles, descriptions, tags, view counts and publishing dates. Private YouTube Studio metrics like watch time and impressions are not part of this connection. **Why does Claude say it cannot access YouTube after setup?** The usual cause is an expired or revoked authorization in Composio. Open Composio, go to Apps, check that YouTube shows as connected, and sign in with Google again if it does not.