We've made significant enhancements to the original prompts-mcp-server that could benefit the community. Here's a plan for contributing these improvements back to the upstream repository.
- Fetch prompts directly from GitHub repositories
- No local storage required (optional backwards compatibility)
- Support for private repos with token authentication
- Recursive directory traversal
- Real-time sync with GitHub
- Clear workflow guidance (search → get → create)
- Intelligent error messages with suggestions
- Comprehensive help system with topics
- Examples in tool schemas
- Anti-pattern prevention
- Semantic search capabilities
- Category and tag-based filtering
- Similar prompt suggestions
- Usage statistics tracking
- Recent prompts feature
- Combine multiple prompts
- Dynamic template variables
- Handlebars support
- Custom separators
- Enhanced TypeScript types
- Comprehensive error handling
- Modular architecture improvements
- Better tool descriptions
Create an issue in the upstream repo to discuss enhancements:
Title: Enhancement Proposal: GitHub Integration and Advanced Features
Hi @tanker327!
I've been using prompts-mcp-server and built some enhancements that might be valuable to the community. I'd love to contribute them back if you're interested.
Key enhancements include:
- GitHub integration for fetching prompts from repositories
- Enhanced AI guidance with workflow recommendations
- Advanced search with category/tag filtering
- Prompt composition capabilities
- Improved error handling with suggestions
These are backwards compatible and include comprehensive tests. Would you be interested in these features? I'm happy to submit them as separate PRs for easier review.
You can see the implementation at: https://github.com/jezweb/smart-prompts-mcpBased on maintainer feedback, create focused PRs:
- Improved tool descriptions with examples
- Help system implementation
- Better error messages
- Small, easy to review
- Basic GitHub fetching capability
- Configuration for GitHub repos
- Backwards compatible with local storage
- Comprehensive tests
- Category and tag filtering
- Search improvements
- Similar prompt suggestions
- Usage tracking
- Combine prompts feature
- Template variable support
- Dynamic composition
- Update README with new features
- Add examples for GitHub integration
- Document configuration options
- Add migration guide
- Keep local file storage as default
- GitHub integration as opt-in feature
- No breaking changes to existing API
- Match existing TypeScript patterns
- Follow current test structure
- Maintain modular architecture
- Add tests for all new features
- Maintain existing test coverage
- Include integration tests
For each PR:
- Tests pass (
npm test) - TypeScript builds (
npm run build) - Documentation updated
- Backwards compatible
- Follows existing code style
- Includes examples
- Create Issue: Open discussion with maintainer
- Prepare Branches: Create feature branches for each PR
- Start Small: Begin with tool descriptions PR
- Iterate: Respond to feedback and adjust
If the maintainer prefers, we could:
- Maintain our fork as a "GitHub-enhanced" version
- Document it as an alternative implementation
- Keep both projects with clear differentiation
- Cross-reference in documentation
- More Storage Options: Local files OR GitHub repos
- Better AI Experience: Clear guidance reduces confusion
- Advanced Features: Search, compose, track usage
- Enterprise Ready: Private repo support
- Active Development: Two maintainers instead of one