Vidlens Mcp

io.github.rajanrengasamyPublished by GitHub account rajanrengasamyv1.2.6Updated Oct 24, 2026

YouTube intelligence layer for AI agents. 41 tools, 10 modules, zero config.

VerifiedSTDIODesktop onlyWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

Vidlens MCP is a local stdio server that gives AI assistants a YouTube intelligence layer with 41 tools across 10 modules.

What you can do
  • The manifest lists no individual tools, so capabilities come from the registry description only.
  • It presents itself as a YouTube intelligence layer for AI agents, exposing 41 tools grouped into 10 modules.
  • It is advertised as zero config, so it can be used without setting up credentials first.
  • Optional keys enable AI-generated visual descriptions and official YouTube Data API access.
When to use it
Worth considering when an assistant needs to work with YouTube content — channels, videos or related data — and you want that capability available locally without a hosted service. The lack of a tool list means you should check the package's own documentation before relying on specific features.
Requirements
Runs as a local process over stdio, installed from the npm package vidlens-mcp, so Node.js is needed. Two optional secrets can be supplied as environment variables: GEMINI_API_KEY for AI-powered visual descriptions and YOUTUBE_API_KEY for the YouTube Data API v3; without the latter it falls back to scraping. Desktop only; no web executable.
Before you install
Both environment variables are secrets: GEMINI_API_KEY and YOUTUBE_API_KEY, and providing them exposes those credentials to the local process. Without YOUTUBE_API_KEY the server falls back to scraping, which may be less reliable and subject to site terms. The manifest declares no authentication and lists no tools, so review the package before installing.

Installation

In SourceWeft

  1. Open Vidlens Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.6LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.