YouTube vs Openshorts

A side-by-side look at the YouTube and Openshorts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

YouTube logoYouTubeSocial Media · Local subprocess (stdio)Extract and convert YouTube video information.44FairAuth: api key requiredOpenshorts logoOpenshortsSocial Media · Local subprocess (stdio)Turn long videos into viral vertical shorts and publish them to TikTok, Instagram and YouTube.48FairAuth: not declared

Verdict: choose YouTube for social media work as a local process; choose Openshorts for social media as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

YouTube logoChoose YouTube when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: API_KEY.
Explore YouTube

Openshorts logoChoose Openshorts when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
Explore Openshorts

Feature & specification comparison

Rows where the two servers differ are marked.

SpecYouTube logoYouTubeOpenshorts logoOpenshorts
CategorySocial MediaSocial Media
Quality signal44/100 · Fair48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsAPI_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,8237,047
Directory activity 4 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

YouTube tools

No tool names declared yet. Check the project README from the listing page.

Openshorts tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

YouTube

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "klavis-ai-youtube": {
      "command": "uvx",
      "args": [
        "klavis"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Openshorts

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openshorts": {
      "command": "uvx",
      "args": [
        "openshorts"
      ]
    }
  }
}

Frequently asked questions

YouTube is categorized under Social Media and uses a local stdio subprocess. Openshorts belongs to Social Media and uses a local stdio subprocess. Pick YouTube for social media work and Openshorts for social media.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

YouTube is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Openshorts has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add klavis-ai-youtube and openshorts as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, YouTube has a quality signal of 44/100 (Fair) with 4 views, 0 installs and 5,823 GitHub stars. Openshorts has 48/100 (Fair) with 2 views, 0 installs and 7,047 GitHub stars.