miduconf

This MCP server exposes a set of YouTube-related tools implemented in a modular fashion. The server is written in TypeScript and compiles to JavaScript under dist, and it registers a collection of tools (for example, search_videos and search_playlists) that a language model or client can invoke via the MCP protocol. The codebase demonstrates how to structure tools as small functions that receive the server instance and register themselves with registerTool, enabling the model to request video searches, playlist searches, and related YouTube data through well-defined, safe tool boundaries. To interact with the server, you typically run the built server locally and connect a suitable MCP client (such as the official inspector) over stdio. The README also shows how to configure the server for VS Code integration and how to test the tools manually.

Prerequisites:

• Node.js (LTS) and npm installed on your system
• Git installed

1. Clone the repository:

git clone https://github.com/0GiS0/0gis0-miduconf-mcp.git
cd miduconf

2. Install dependencies:

npm install

3. Build the MCP server (TypeScript to JavaScript in dist):

npm run build

4. Run the MCP server locally:

node dist/index.js

5. Optional: test with the MCP Inspector client:

npx @modelcontextprotocol/inspector

6. If you register API keys or environment variables, create an .env file or set them in your environment. For example, the server expects a YouTube API key to access certain tools.

# Example .env
YOUTUBE_API_KEY=your_youtube_api_key_here

6. If you modify the code, re-run the build step to update dist:

npm run build

Tips and caveats:

• The server uses stdio transport by default, so tools are exposed through the MCP protocol rather than a web API.
• You can add more YouTube-related tools by following the pattern in src/tools/youtube (e.g., searchVideos, searchPlaylists) and registering them from the appropriate index.ts file.
• Ensure you copy .env-sample to .env and set your API keys (as indicated in the README) if you rely on external APIs.
• The configuration example in this documentation uses a single MCP server named miduconf; you can expand with additional servers by adding more entries under mcpServers.
• The npm package name is not specified in this repository; if you publish it, specify the package name in npm_package. Otherwise this field remains null.