nerdearla

This MCP server bundle provides three demonstrations of MCP-powered tools centered around YouTube content interaction and generative capabilities. The tools expose an MCP-compliant interface that lets you search for videos, engage in interactive elicitations to refine user intent, and generate creative video titles using model-assisted sampling. Specifically, you can access:

• Search Video: a basic tool that retrieves YouTube videos matching a query. It demonstrates input validation, external API calls, robust error handling, and returning MCP-formatted results.
• Search Channel: an interactive tool that finds YouTube channels and engages the user through elicitation prompts to decide whether to fetch the channel’s latest videos. This showcases bidirectional dialogue, dynamic schema validation, and client-server communication features.
• Generate Video Title: an advanced creative tool that delegates title generation to the model, guiding the user through language selection and producing multiple creative title variants via sampling. These tools illustrate how to structure MCP tool definitions, validate inputs with schemas, call external services, and compose responses suitable for downstream MCP clients. To experiment, initialize the server and invoke each tool through your MCP client, observing the validation, dialog flows, and multi-result outputs that the server returns.

Prerequisites:

• Node.js (LTS) and npm installed on your machine
• Git (optional, for cloning the repo)

Install and run:

1. Clone or download this MCP server repository to your machine.
2. Install dependencies (from the repository root):

npm install

3. Build if a build step is required (consult package.json scripts). If there is a TypeScript source, you may need:

npm run build

4. Run the MCP server:

npm start

5. Connect an MCP client to the running server endpoint and begin invoking the tools: Search Video, Search Channel, and Generate Video Title. If using npx as configured in mcp_config, the server will be launched via the package name when needed.

Notes:

• If the repository uses a different startup script, replace npm start with the exact command shown in the package.json scripts section (for example, node dist/server.js).
• Ensure any required API keys (e.g., YouTube Data API) are provided as environment variables as the server’s tools implement external service calls.

Tips and caveats:

• YouTube API usage may require an API key. If the tools reference the API, set the key in an environment variable (e.g., YT_API_KEY) or as documented by the repository.
• The Search Channel tool uses elicitation flows; be prepared to respond to prompts that refine what content you want (e.g., channel filters, latest videos).
• Tool outputs are structured to fit MCP response schemas; when integrating with clients, ensure your client handles validation errors and dialog state transitions gracefully.
• If you encounter schema validation errors, verify that inputs conform to the expected shapes defined in the tool schemas (e.g., required fields for query or selection enums).
• If running in a containerized environment, you may prefer the docker command form or adapt the npm start script to your orchestration workflow.