pulsemcp verified Safe content atomic mcp-remote

YouTube Data API

This MCP server provides AI assistants with complete YouTube API access and management capabilities, built by eat-pray-ai using Go with Cobra CLI framework and featuring both command-line interface and MCP server modes for programmatic YouTube operations. The implementation offers full CRUD operations across all major YouTube resources including videos, playlists, channels, comments, captions, subscriptions, and analytics data, with support for video uploads, thumbnail management, live streaming controls, and content moderation workflows through the official Google YouTube Data API v3. Built with Bazel build system, Docker containerization, OAuth2 authentication with token caching, flexible output formats (JSON, YAML, table), and JSONPath filtering capabilities, it serves content creators needing conversational access to YouTube channel management, social media managers requiring AI-driven video publishing and analytics workflows, and development teams where natural language interfaces enhance YouTube integration without direct API knowledge.

Cognium trust score

95%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/eat-pray-ai/yutu
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve YouTube Data API from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"