# How to connect YouTube to Grok Bot (no API keys) > Connect YouTube to Grok Bot with ClawLink in one click — 47 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/youtube Grok Bot runs on its own cloud computer, so most YouTube guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical YouTube setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real YouTube actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect youtube` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to YouTube. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect YouTube** — `npx -y @useclawlink/cli connect youtube`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect youtube # connect YouTube (browser OAuth) npx -y @useclawlink/cli actions youtube # list available actions npx -y @useclawlink/cli run youtube --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect youtube ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use YouTube to add video to playlist and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once YouTube is connected in the dashboard, that agent calls the same 47 YouTube tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## YouTube MCP for Grok Bot Looking for a YouTube MCP server for Grok Bot? ClawLink connects YouTube to Grok Bot and exposes 47 YouTube tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw YouTube integration](https://claw-link.dev/openclaw/youtube) and the [Hermes YouTube integration](https://claw-link.dev/hermes/youtube) connect the same ClawLink account the same way. ## What the Grok Bot YouTube integration can do 47 YouTube tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 47. ### 30 of 47 YouTube tools for Grok Bot | Tool | What it does | |---|---| | **Add video to playlist** `youtube_add_video_to_playlist` | Add a video to a YouTube playlist | | **Create comment reply** `youtube_create_comment_reply` | Reply to a YouTube comment | | **Create playlist** `youtube_create_playlist` | Create a YouTube playlist | | **Get channel activities** `youtube_get_channel_activities` | List YouTube channel activities | | **Get channel statistics** `youtube_get_channel_statistics` | Get YouTube channel statistics | | **Get video details batch** `youtube_get_video_details_batch` | Get YouTube video metadata | | **List channel videos** `youtube_list_channel_videos` | List YouTube videos for a channel | | **List comment threads2** `youtube_list_comment_threads2` | List YouTube comment threads | | **List comments** `youtube_list_comments` | List YouTube comments | | **List user playlists** `youtube_list_user_playlists` | List YouTube playlists | | **Multipart upload video** `youtube_multipart_upload_video` | Upload a large video to YouTube via multipart | | **Post comment** `youtube_post_comment` | Post a comment on a YouTube video | | **Rate video** `youtube_rate_video` | Rate a YouTube video | | **Search you tube** `youtube_search_you_tube` | Search YouTube videos and channels | | **Subscribe channel** `youtube_subscribe_channel` | Subscribe to a YouTube channel | | **Unsubscribe channel** `youtube_unsubscribe_channel` | Unsubscribe from a YouTube channel | | **Update playlist** `youtube_update_playlist` | Update a YouTube playlist | | **Update video** `youtube_update_video` | Update YouTube video metadata | | **Upload video** `youtube_upload_video` | Upload a video to YouTube | | **Get channel ID by handle** `youtube_get_channel_id_by_handle` | Retrieves the YouTube Channel ID for a specific YouTube channel handle | | **Get video rating** `youtube_get_video_rating` | Retrieves the ratings that the authorized user gave to a list of specified videos | | **List caption track** `youtube_list_caption_track` | Retrieves a list of caption tracks for a YouTube video | | **List channel sections** `youtube_list_channel_sections` | Retrieve channel sections from YouTube | | **List i18n languages** `youtube_list_i18n_languages` | Returns a list of application languages that the YouTube website supports | | **List i18n regions** `youtube_list_i18n_regions` | Retrieve a list of content regions that the YouTube website supports | | **List live chat messages** `youtube_list_live_chat_messages` | List live chat messages for a specific chat | | **List playlist images** `youtube_list_playlist_images` | Retrieve playlist images associated with a specific playlist | | **List playlist items** `youtube_list_playlist_items` | List videos in a playlist, with pagination support | | **List super chat events** `youtube_list_super_chat_events` | Lists Super Chat events for a channel, showing supporter purchases during live streams | | **List user subscriptions** `youtube_list_user_subscriptions` | Retrieves the authenticated user's YouTube channel subscriptions, allowing specification of | ## Example prompts **Add Video To Playlist** > Use YouTube to add video to playlist and walk me through the result in plain English. **Create Comment Reply** > Create it in YouTube for me, then confirm the important fields before you finish. **Create Playlist** > Create it in YouTube for me, then confirm the important fields before you finish. **Get Channel Activities** > Pull the relevant data from YouTube, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want YouTube working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a YouTube app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect YouTube through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for YouTube. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right YouTube actions to the runtime in a format your agent can reliably use. | 47 tools for YouTube are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes YouTube to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect YouTube in the browser, and the 47 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect YouTube from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling YouTube tools YouTube tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every YouTube call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### YouTube returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting YouTube and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot YouTube integration? Yes. ClawLink is the fastest way to connect Grok Bot to YouTube: link your YouTube account once in the browser and Grok Bot can call the YouTube API through 47 ready-made tools — no custom code or token handling. ### How do I connect YouTube to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect youtube` to authorize YouTube. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect YouTube to Grok Bot? About two minutes. Sign in, click Connect next to YouTube in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring YouTube up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want YouTube working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Stack Exchange tools](https://claw-link.dev/grokbot/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Zernio](https://claw-link.dev/grokbot/zernio) — Schedule social posts and pull analytics across platforms - [Grok Bot Facebook integration](https://claw-link.dev/grokbot/facebook) — Read Facebook Page posts and engagement