Vidalytics MCP vs Tube Search MCP

In-depth architectural comparison of the Vidalytics MCP and Tube Search MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Vidalytics MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: set_user_context, list_videos, get_video.

Explore Vidalytics MCP Details

Choose Tube Search MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_channel, search_videos, get_video.

Explore Tube Search MCP Details

Feature & Specification Comparison

Specification	Vidalytics MCP vidalytics Developer Tools	Tube Search MCP Developer Tools
Summary	Manage your Vidalytics videos and analytics from your AI assistant.	Search archived YouTube videos including deleted, private, or region-blocked content.
Category & Scope	Developer Tools	Developer Tools

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "mcp-272": {
      "command": "npx",
      "args": [
        "-y",
        "@vidalytics/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "tube-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tube-search-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons