Spaces:
Running
Running
| - [x] Join the Agents-MCP-Hackathon organization on Hugging Face. (https://huggingface.co/Agents-MCP-Hackathon) | |
| - [x] Complete the registration form before June 8 2025 11:59 PM UTC | |
| - [x] (MCP track selected)Decide on one of three tracks: MCP Server/Tool, Custom Component, or Agentic Demo. | |
| - [x] (https://huggingface.co/blog/gradio-mcp) Download or clone the relevant starter template (MCP server boilerplate, custom component template, or basic agent demo). | |
| - [x] Review the "Getting Started with MCP with Gradio" and "Gradio Component Development Guide" documentation. | |
| - [ ] Generate and review relevant ChatGPT research papers. (Researching a Winning Project Idea for the Gradio Agents & MCP Hackathon 2025 | Strategy to Win the MCP Tool/Server Hackathon Track | Using Your RTX 2060 Instead of Cloud APIs for the MCP Hackathon) | |
| - [ ] Set up a local development environment with Python, Gradio 5, and any required SDKs (OpenAI, Anthropic, etc.) using provided API credits. | |
| - [ ] Implement the required features: | |
| - [ ] For Track 1, build a Gradio app that functions as an MCP server and test with an MCP client. | |
| - [ ] For Track 2, create a custom Gradio component, publish it with gradio cc publish, and verify functionality. | |
| - [ ] For Track 3, develop a Gradio app showcasing agentic behavior or integrations. | |
| - [ ] Create a Space in Hugging Face for your project. | |
| - [ ] Populate the Space's README.md with the mandatory track tag (mcp-server-track, custom-component-track, or agent-demo-track). | |
| - [ ] Record a demonstration video of your app or component in action; host it on YouTube or similar. | |
| - [ ] Insert the link to the demonstration video in README.md. | |
| - [ ] Push all code and documentation to your Space before June 8 2025 11:59 PM UTC. | |
| - [ ] Verify that your Space runs properly online; confirm video link accessibility. | |
| - [ ] Monitor Discord and office hours for troubleshooting; resolve any issues immediately. | |
| - [ ] Submit the final Space entry; ensure compliance with hackathon policies and original work requirements. |