onemcp-hub

OneMCP Hub is a central GitHub-backed hub for OneMCP users to report issues, request features, and propose new MCPs. It serves as the coordinating space where templates guide users to submit Bug Reports, Feature Requests, and New MCP Proposals, and where the community and OneMCP team track statuses through labeled issues. To use it, navigate to the repository's Issues tab and select the appropriate template based on what you want to contribute. Bug Reports help identify unexpected behavior and reproducible steps, Feature Requests propose new capabilities and their value, and New MCP Proposals describe planned MCPs with use cases and potential implementations. The issue labels (triage, accepted, in-progress, needs-more-info) help you understand where a submission stands in the review and development workflow.

Prerequisites:\n- Access to the GitHub repository: https://github.com/ipenywis/onemcp-hub\n- A Git client installed on your machine (git) and basic command-line knowledge\n\nStep-by-step: \n1) Clone the repository locally:\nbash\ngit clone https://github.com/ipenywis/onemcp-hub.git\ncd onemcp-hub\n\n2) Review contribution guidelines and templates located in the repository (e.g., .github/ISSUE_TEMPLATE).\n3) Create a new issue using the appropriate template on GitHub:\n- Bug Report: describe steps to reproduce, expected vs actual behavior, environment details.\n- Feature Request: describe the feature, value, and acceptance criteria.\n- New MCP Proposal: provide name, description, use cases, benefits, and any sample implementation or references.\n4) Optionally fork the repo, make changes to documentation or templates, and submit a pull request if you contribute improvements to the hub itself.\n\nNote: This repository is a community hub and does not deploy as a standalone runtime server. Interactions happen via GitHub issues, not a running MCP server process.

Tips and considerations:\n- Use clear, reproducible steps when filing Bug Reports. Include environment details such as OneMCP versions and platform information.\n- When proposing a new MCP, outline the name, description, concrete use cases, benefits, and any sample implementation notes.\n- Be mindful of the issue labels to understand status at a glance: triage, accepted, in-progress, needs-more-info.\n- The repository is licensed under MIT; adhere to contributing guidelines and maintain respectful, constructive communication.\n- If you’re unsure where to file something, start with a Bug Report or Feature Request template to guide the process.\n- This hub serves as a centralized discussion and tracking area rather than a runtime server; there is no executable startup command for this project.