Maagpi Youtube MCP Server

Maagpi Youtube MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Maagpi Youtube MCP directly instead of describing what you should do. YouTube Data API v3 + Analytics API MCP server — full channel management for AI agents.

What you get

Wraps the official YouTube Data API v3 + YouTube Analytics API behind a single MCP surface with built-in OAuth, quota tracking, response caching, and structured error handling.

• Operate YouTube from any AI client — — Claude, Cursor, Windsurf, Zed, VS Code, mcporter
• Manage multiple channels at once — — no context switching, target any channel per call
• Production-grade plumbing — — OAuth, refresh tokens, quota tracking, retries, structured errors
• Full surface coverage — — videos, scheduling, analytics, comments, playlists, branding

Setting it up

Installation goes through your MCP client rather than a global install: point it at maagpi-youtube-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once Maagpi Youtube MCP is connected, these are the calls the assistant has available:

• Default — ** stdio (local process, spawned by your MCP client)
• Optional — ** Streamable HTTP (YOUTUBE_MCP_TRANSPORT=http) for multi-client / remote access
• Distribution — ** npx maagpi-youtube-mcp — no global install required
• Production — grade plumbing** — OAuth, refresh tokens, quota tracking, retries, structured errors
• youtube_account_add — name
• youtube_account_list — none
• youtube_account_switch — name
• youtube_account_current — none
• youtube_account_remove — name, confirm: true
• youtube_video_upload — filePath, title, privacyStatus, channel?
• youtube_video_get — videoId, parts?, channel?
• youtube_video_list — channelId?, query?, order?, maxResults?, channel?

Configuration and credentials

You will need 3 environment variables: YOUTUBE_CLIENT_ID, YOUTUBE_CLIENT_SECRET, YOUTUBE_MCP_HTTP_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Maagpi Youtube MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the maagpi youtube mcp mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Maagpi Youtube MCP's toolset — Default, Optional, Distribution and 11 more — is a fair guide to whether it matches your workflow. It is maintained by vamsi-kodimela; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.