go_mcp_server_youtube_search

Created By
hightempa year ago
A simple MCP (Model Context Protocol) server that provides tools for searching and retrieving information from YouTube videos. This server can be used with AI assistants that support the MCP protocol.
Overview

go_mcp_server_youtube_search is a simple MCP (Model Context Protocol) server designed to provide tools for searching and retrieving information from YouTube videos. It can be integrated with AI assistants that support the MCP protocol.

To use the server, run it in either stdio or sse mode. The default mode is sse. You can start the server with the following command:

 go_mcp_server_youtube_search -t sse -h 0.0.0.0 -p 8889
# or
 go_mcp_server_youtube_search -t stdio
  • youtube_search: Search for YouTube videos using a text query.
  • youtube_get_video_info: Retrieve detailed information about a video by its ID.
  • youtube_get_subtitles: Get video subtitles in English or Russian.
  1. Integrating YouTube search capabilities into AI assistants.
  2. Retrieving detailed video information for content analysis.
  3. Accessing subtitles for videos to enhance accessibility.
  • Can I use this server with any AI assistant?

Yes! The server is designed to work with any AI assistant that supports the MCP protocol.

  • What programming language is this server written in?

The server is written in Go.

  • Is there a graphical interface for this server?

No, the server operates through command line and does not have a graphical interface.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hightemp
Star
3
Language
Go
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago