idosal
Repository Configuration Suggestions for Better MCP Content
Hello! I would like to know what kind of repository setup can help generate better MCP content. Could you provide a list of repository configuration suggestions? Here are some of my questions:
- For frontend projects, does having .d.ts definition files significantly impact the quality of MCP content?
- Should we include a .github/prompt file in the repository? Does it improve MCP content generation?
- Are there any other configurations that could affect MCP content?
Looking forward to your response! Thank you!
Hey @shawn0326 , those are great questions! We're testing for the optimal parameters, and we'll share the results and guidelines as we get concrete signals.
In parallel, we're working on a feature that'd allow repositories to customize and enhance the way MCPs (starting with GitMCP) access and externalize their documentation (think along the lines of defining an .mcp file in the repo). We're actively looking for project maintainers to contribute to this standard. We'd love to hear your thoughts, requirements, and ideas!
That's amazing! I'm not deeply experienced in this area, but what you're doing excites me: future codebases will cater to both humans and AI, and you're lowering the barriers to make this a reality—this could even spark an ecosystem!
I'd love to discuss my needs. I'm currently maintaining a Web3D rendering library, and I hope AI can leverage it to help me build more applications. An MCP Server seems like a convenient choice. However, current AI systems often exhibit hallucinations, providing feedback based on APIs from other popular libraries. I hope that with some form of configuration, AI can become more familiar with my codebase. I could offer relevant configurations in the repository, such as documentation, .d.ts files, and prompt files.
By the way, one more question: have you considered generating MCP Servers based on NPM packages instead of GitHub repositories? The reason is that NPM packages often include more comprehensive documentation, .d.ts declaration files, etc. On the other hand, the best practices for GitHub repositories often involve ignoring these files during commits. If such files are essential, it leaves me torn (e.g., I'm currently debating whether to upload auto-generated .d.ts files to GitHub...).