biznagafest

BiznagaFest MCP server provides a small suite of example tools that demonstrate core MCP Server capabilities: basic search, interactive elicitation, and creative content generation. The demos are designed to show how to structure tools with validation schemas, call external services (like YouTube in the examples), handle errors robustly, and return properly formatted MCP responses. You can run the server locally and interact with the included tools to see how a client would request data, prompt the user with elicitations, and receive multiple creative outputs generated by a model.

Once running, you can invoke tools such as: - Search Video: fetches YouTube videos based on a query. - Search Channel: interactively queries channel data and asks the user if they want the latest videos. - Generate Video Title: uses a model to generate multiple creative video titles in the user’s preferred language. These tools illustrate how to structure inputs, perform validation, and manage conversation flow with elicitations to gather user preferences before performing actions.

The MCP server exposes a simple API surface for these demos, making it straightforward to extend with additional tools or replace the sample data with real services as needed.

Prerequisites:\n- Node.js (16.x or newer) and npm/yarn installed on your machine.\n- Basic familiarity with running Node.js applications.\n\nStep-by-step:\n1) Clone the repository or download the code.\n2) Navigate to the project directory.\n3) Install dependencies:\nbash\nnpm install\n# or\nyarn install\n\n4) Configure environment variables (example):\nbash\nexport MCP_LOG_LEVEL=info\nexport MCP_BASE_URL=http://localhost:3000\nexport MCP_API_KEY=your-api-key-if-needed\n\n5) Start the MCP server:\nbash\nnpm start\n# or\nnode src/server.js\n\n6) Open the MCP console or client and begin exploring the demo tools.\n\nNotes:\n- If you customize tools, ensure their input/output schemas align with MCP expected shapes.\n- Adjust environment variables as needed for your deployment (base URL, authentication, logging level).

Tips and common issues:\n- Ensure your Node.js version is compatible with the project dependencies.\n- If the server fails to start, check that the port (default 3000) is not in use and that environment variables are correctly set.\n- When wiring to external services (e.g., YouTube), consider adding rate limiting and error handling to prevent cascading failures.\n- Use descriptive validation schemas for tool inputs to catch invalid data early.\n- For production deployments, consider configuring proper authentication, secret management, and logging.\n\nEnvironment variables references (examples): MCP_BASE_URL for the server base URL, MCP_API_KEY for optional API authentication, MCP_LOG_LEVEL for log verbosity.