Youtube Studio MCP Server

Connect Youtube Studio MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A local Model Context Protocol (MCP) server for managing YouTube channels from AI tools such as Codex, Claude Desktop, Cursor, and other MCP-compatible clients. The youtube studio mcp mcp server is what makes that connection.

What the server does

• Read authenticated channel profile, statistics, branding, and uploads playlist
• List recent videos with metadata, privacy status, content details, and public stats
• Update video title, description, tags, category, default language, and privacy status
• Upload custom thumbnails from local image files
• Read channel and per-video YouTube Analytics reports
• Post and list top-level video comments

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• youtube_channel_overview — youtube_list_videos
• youtube_get_video — youtube_update_video
• youtube_upload_thumbnail — youtube_channel_analytics
• youtube_video_analytics — youtube_post_comment

Credentials and setup notes

Configuration is passed through the environment: YOUTUBE_CLIENT_SECRETS, YOUTUBE_TOKEN_FILE, VIDEO_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10 or newer. - A Google account with access to the YouTube channel. - A Google Cloud project with: - YouTube Data API v3 enabled. - YouTube Analytics API enabled. - A Google OAuth Desktop app client JSON. - An MCP-compatible client.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Youtube Studio MCP's toolset — youtube_channel_overview, youtube_get_video, youtube_upload_thumbnail and 1 more — is a fair guide to whether it matches your workflow. It is maintained by i1s-abhishek; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.