Youtube Mcp

YouTube MCP

A local-first MCP server that lets AI assistants search YouTube, manage your channel and read your analytics, and asks you to approve changes to your channel and content first.

[License: MIT] [Node.js >=22.13] [MCP server]

YouTube MCP is a Model Context Protocol server written in TypeScript. It exposes 79 tools to MCP clients such as Claude Code, Claude Desktop, Cursor and Codex. It runs on your own machine over stdio, keeps its OAuth tokens and working data on your disk, and never starts a network listener unless you ask for one.

Anything that changes your YouTube account goes through a preflight, approve, execute flow. The assistant first shows you exactly what it is about to do, and nothing happens until the exact previewed change is approved.

Quick start

1. Get your keys. Follow the beginner setup guide (5 minutes for public research, about 15 with your own channel).
2. Install in your agent. Pick yours in Install in your AI agent.
3. Sign in once (only for your own channel): run the youtube-auth command in Account and creator tools.
4. Ask your agent: "Check my YouTube auth status", then "Search YouTube for talks about MCP".

What it can do

Read (no account needed, just an API key)

• Search videos (with order, date, duration, channel, region and safe-search filters), see what is trending, list the recent uploads of any channel, look up videos and channels.
• List the public comments on a video.
• Fetch a public transcript (best effort; some videos have none).

Read (your own account and channel, via OAuth)

• Your channel, your subscriptions, and comment threads on your channel.
• Creator analytics: channel overview, top videos and audience retention for a date range, plus a flexible report (views by day, traffic sources, devices, countries, demographics and more).
• Your uploaded videos, playlists and playlist items, caption tracks, and the comment moderation queue.

Write (your own account; channel and content changes need preview and approval, viewer actions need confirm: true)

• Uploads: resumable video uploads, with status check, resume and cancel. Uploads are private unless you explicitly ask to publish.
• Videos: update title, description and other metadata, and set thumbnails.
• Captions: upload, update, download and delete caption tracks.
• Playlists: create, update, delete, and add, remove or reorder items. New playlists default to private.
• Comments and moderation: reply to comments, set a moderation status (including banning an author), and delete comments on your channel.
• Channel profile: edit your channel description, keywords, country and default language.
• Subscription curation: review subscriptions with subscriber counts and last upload date, then remove many at once after one approval.
• Account actions: subscribe, unsubscribe, rate a video, post a top-level comment (these need a literal confirm: true).

Private viewing analysis (local only)

• Import your Google Takeout YouTube history and get a profile and trend comparison between two date ranges. The data stays in a local SQLite file.
• Save local curation allowlists and generate a finite, proposed queue. The server never applies a queue to your account.

Safety model

Write tools are built so an AI client cannot make a surprise change:

1. Preflight. A youtube_preflight_* tool reads fresh state from YouTube, validates the request and returns an exact preview.
2. Approve. A separate youtube_approve call (one tool for every kind of change), with confirm: true, binds approval to the profile, channel, target, requested change and fresh state. Approvals expire. They are stored locally, so an approved operation survives a server restart until it expires.
3. Execute. The write tool runs only with the same approved inputs and confirm: true.

More guard rails, all from the code:

• Viewer actions (youtube_subscribe, youtube_unsubscribe, youtube_rate_video), youtube_create_comment and the local curation and reset tools are single-step writes: no preflight, but they require a literal confirm: true.
• Mutations are never retried automatically. Ambiguous outcomes are reconciled with a read.
• Public visibility, scheduling, synthetic-media changes and banning an author need an explicit, elevated flag.
• Comment deletion requires the comment to belong to your selected channel.
• Caption downloads never overwrite an existing path or follow symbolic links.
• Creator tools check that the signed-in Google account matches the channel ID you configured.
• The automated tests never make a live mutation.

Full details are in docs/README.md.

Requirements

• Node.js 22.13 or newer
• A Google Cloud project with the YouTube Data API v3 enabled (and the YouTube Analytics API for the creator analytics tools)
• A YouTube Data API key for public reads, and an OAuth desktop client for account and creator tools

Install in your AI agent

No npm publish is needed. Every route below runs the server from the prebuilt tarball attached to the GitHub release with npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz --transport stdio, except the Claude Desktop bundle, which carries its own copy. You need Node.js 22.13+ on your PATH for the npx routes. Create your Google credentials first with the beginner setup guide (short version: Google credentials). You need at least a YouTube Data API key.

Ready-made files for each client are in configs/. Use the placeholders as shown and never paste a real key into a file you commit.

The first launch downloads the prebuilt release tarball and installs its dependencies, which takes a few seconds on a normal connection. Later launches use npm's cache. To be safe against a client start-up timeout on a slow network, warm the cache once in a terminal first:

npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz --version

Claude Code

claude plugin marketplace add pratikgh0se/youtube-mcpclaude plugin install youtube-mcp@youtube-mcp

Or inside Claude Code: /plugin marketplace add pratikgh0se/youtube-mcp, then /plugin install youtube-mcp@youtube-mcp. Claude Code asks for your API key (stored in your OS credential store) and four more settings: OAuth client file, profile name and channel ID are required, and the state directory is optional (leave it blank to use ~/.youtube-mcp). The plugin only holds config. The server itself still runs through npx.

Claude Desktop

Download youtube-mcp-<version>.mcpb (one universal bundle for macOS, Windows and Linux) from GitHub Releases and double-click it. Claude Desktop shows an install dialog and asks for your API key. The bundle includes the server, so it needs no npx at run time.

Fallback if you prefer not to use the bundle: add configs/claude-desktop.json to claude_desktop_config.json and restart. The first start downloads the package, which can take a few seconds.

{  "mcpServers": {    "youtube-mcp": {      "command": "npx",      "args": ["-y", "https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz", "--transport", "stdio"],      "env": { "YOUTUBE_API_KEY": "<your-youtube-api-key>" }    }  }}

Codex CLI

codex mcp add youtube-mcp --env YOUTUBE_API_KEY=<your-youtube-api-key> -- npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz --transport stdio

That stores the key in ~/.codex/config.toml. To keep it out of the file, use configs/codex.toml instead. It forwards the variables from your shell with env_vars (Codex does not expand ${VAR}) and sets startup_timeout_sec = 180, because the default of 10 seconds is shorter than the first npx run.

[mcp_servers.youtube-mcp]command = "npx"args = ["-y", "https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz", "--transport", "stdio"]env_vars = ["YOUTUBE_API_KEY"]startup_timeout_sec = 180

Gemini CLI

gemini extensions install https://github.com/pratikgh0se/youtube-mcp

Gemini prompts for your API key (kept in the system keychain, required) and the OAuth client file, profile name and channel ID (needed for your channel's tools; see the setup guide). Change them later with gemini extensions config youtube-mcp. A plain settings.json entry is in configs/gemini-settings.json.

Note: Google stopped serving Gemini CLI to AI Pro, Ultra and free individual users on 2026-06-18. Paid API-key and enterprise users keep it (source). Everyone else should use Antigravity CLI below.

Antigravity CLI

Add this to ~/.gemini/config/mcp_config.json (global) or <workspace>/.agents/mcp_config.json. It is also in configs/antigravity.json.

{  "mcpServers": {    "youtube-mcp": {      "command": "npx",      "args": ["-y", "https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz", "--transport", "stdio"],      "env": { "YOUTUBE_API_KEY": "<your-youtube-api-key>" }    }  }}

Cursor

[Install MCP Server]

The button reads YOUTUBE_API_KEY from your shell environment. Or add configs/cursor.json to .cursor/mcp.json (or ~/.cursor/mcp.json). It uses ${env:YOUTUBE_API_KEY}, so no secret is written to the file.

VS Code / Copilot

[Install in VS Code]

The button installs the server without a key. Add one afterwards through the server's env, or use the file below, which prompts for it. From a terminal:

code --add-mcp '{"name":"youtube-mcp","type":"stdio","command":"npx","args":["-y","https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz","--transport","stdio"]}'

Or save configs/vscode.json as .vscode/mcp.json. VS Code asks for the key on first start (password: true) and stores it securely.

{  "inputs": [    { "type": "promptString", "id": "youtube-api-key", "description": "YouTube Data API v3 key", "password": true }  ],  "servers": {    "youtube-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz", "--transport", "stdio"],      "env": { "YOUTUBE_API_KEY": "${input:youtube-api-key}" }    }  }}

Windsurf

Use configs/windsurf.json (it reads ${env:YOUTUBE_API_KEY}). The current Devin docs put the file at ~/.config/devin/mcp_config.json (Windows: %APPDATA%\devin\mcp_config.json). The older path ~/.codeium/windsurf/mcp_config.json is what many guides still show. Only the first is confirmed by the vendor's docs, so if one does not load, try the other.

Cline

Open the MCP Servers panel, Configure, then "Configure MCP Servers", and add configs/cline.json. For Cline CLI the file is ~/.cline/data/settings/cline_mcp_settings.json. Cline does not document env interpolation, so the key goes in as a literal value in that file. You can also ask Cline to install it from llms-install.md.

Zed

Add configs/zed.json to your Zed settings (run the zed: open settings file action). Zed calls the map context_servers. The key goes in as a literal value.

goose

Run goose configure, choose Add Extension, then Command-Line Extension, and enter npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz --transport stdio with the key as an environment variable. Or add configs/goose.yaml to ~/.config/goose/config.yaml. The deeplink form (paste it into a browser or open) sets only the command, so add the key afterwards:

goose://extension?cmd=npx&arg=-y&arg=https%3A%2F%2Fgithub.com%2Fpratikgh0se%2Fyoutube-mcp%2Freleases%2Fdownload%2Fv0.3.2%2Fyoutube-mcp-0.3.2.tgz&arg=--transport&arg=stdio&id=youtube-mcp&name=YouTube%20MCP&description=Search%20YouTube%20and%20manage%20your%20channel%20with%20approval%20for%20every%20change

Other agents

Any client that launches stdio MCP servers can use configs/generic-stdio.json. Templates for OpenCode, OpenClaw and Hermes are in configs/ too. Agents installing this for a user should read AGENTS.md.

Account and creator tools: authorize once

Public tools need only the API key. For account and creator tools, add the OAuth client file, profile name and channel ID from step 2 to your client config, then run the one-time Google sign-in from a terminal with the same values:

YOUTUBE_OAUTH_CLIENT_SECRET_FILE=/absolute/path/to/client_secret.json \YOUTUBE_MCP_PROFILE_ID=creator-main \npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz youtube-auth

This opens a browser for Google consent on a local 127.0.0.1 callback and requests the youtube, youtube.force-ssl and yt-analytics.readonly scopes. The token is stored under ~/.youtube-mcp for that profile, and later calls refresh it silently. Run it again if you revoke access.

Google credentials

1. Create credentials

New to Google Cloud? Use the step-by-step beginner setup guide. The short version:

In the Google Cloud console:

1. Create or pick a project, then enable YouTube Data API v3 and YouTube Analytics API.
2. Create an API key. This is enough for the public tools.
3. For account and creator tools, configure the OAuth consent screen (add yourself as a test user while the app is in testing), then create an OAuth client ID of type Desktop app and download its JSON file.

2. Set environment variables

Put these in your client config (see Install in your AI agent), or copy .env.example to .env (it is git-ignored) when running from a checkout. Never commit real values.

Run from a local checkout

For development, or to run without npx:

git clone https://github.com/pratikgh0se/youtube-mcp.gitcd youtube-mcpnpm cinpm run build   # npm ci already builds via the prepare scriptnpm run auth    # one-time Google sign-in, same as the npx youtube-auth command

Point your client at the checkout with an absolute path:

{  "mcpServers": {    "youtube-mcp": {      "command": "node",      "args": ["/absolute/path/to/youtube-mcp/bin/youtube-mcp.mjs", "--transport", "stdio"],      "env": {        "YOUTUBE_API_KEY": "your-api-key",        "YOUTUBE_OAUTH_CLIENT_SECRET_FILE": "/absolute/path/to/client_secret.json",        "YOUTUBE_MCP_PROFILE_ID": "creator-main",        "YOUTUBE_MCP_CHANNEL_ID": "UC..."      }    }  }}

More templates (one per client) are in configs/. They launch the server with npx -y https://github.com/pratikgh0se/youtube-mcp/releases/download/v0.3.2/youtube-mcp-0.3.2.tgz --transport stdio. To use your checkout instead, change the command to node with the path above.

Optional: local HTTP

PORT=3000 node bin/youtube-mcp.mjs --transport http

This binds to 127.0.0.1 only. Do not expose it to the internet.

Example prompts

• "Search YouTube for recent talks about the Model Context Protocol and summarise the top three."
• "Get the transcript for this video and list the main points."
• "Show my channel's top 10 videos for the last 90 days and where viewers drop off in the most recent one."
• "Preview a private upload of /Users/me/videos/demo.mp4 titled 'Demo', and wait for me to approve it."
• "Create a private playlist called 'To review' and add these five videos to it. Show me the preview first."
• "List the unreplied comments on my latest video and draft replies for me to approve."
• "Import my Takeout watch history and compare what I watched in January with what I watched in June."

Tools

79 tools, grouped by area. Tools marked "preflight and approve" need the three-step flow above.

Privacy and security

• The OAuth refresh token is stored on your machine under ~/.youtube-mcp (or YOUTUBE_MCP_STATE_DIR), in a file with user-only permissions.
• Operation approvals, upload recovery state and your Takeout-derived SQLite database (consumption.sqlite) live in the same directory. The Takeout importer never sends data to YouTube.
• Your Google credentials go only to Google's APIs. The public transcript tool uses the youtube-transcript package to fetch captions from YouTube.
• The default transport is stdio. The optional HTTP transport binds to 127.0.0.1 only.
• Never commit .env, your OAuth client JSON, token state or Takeout exports. The .gitignore already excludes .env files.
• Running this server gives the AI client access to your YouTube account within the scopes you grant. Review each preview before approving it.
• To report a vulnerability, follow SECURITY.md and use GitHub's private reporting. Please do not open a public issue.

Development

npm cinpm run lint            # type check the sourcenpm run typecheck:tests # type check the testsnpm test                # vitest, fully offline (214 tests)npm run build           # compile to dist/npm run smoke:read-only # offline by default; set YOUTUBE_LIVE_SMOKE=1 with an API key for one live readnpm run dev:stdio       # run from source over stdio

Continuous integration (.github/workflows/verify.yml) runs the same checks on Node 22. See docs/CHANGELOG.md for what has changed.

Contributing

Issues and pull requests are welcome. Please run npm run lint, npm run typecheck:tests and npm test before opening a pull request, add tests for any behavior change, and keep write actions behind the preflight and approve flow. Never include real credentials, tokens or personal data in issues, tests or fixtures.

License

MIT (c) 2026 Pratik Ghose