Thank you for considering contributing to the FreshRSS MCP Server! This document provides guidelines and instructions for contributing.
Please read and follow our Code of Conduct.
Before submitting a bug report:
- Check the issue tracker to see if the problem has already been reported
- Ensure you're using the latest version
- Collect relevant information about the issue (error messages, steps to reproduce, etc.)
When submitting a bug report, please include:
- The version of the software you're using
- Your operating system and version
- Detailed steps to reproduce the problem
- Expected behavior and what went wrong
- Any error messages or logs (make sure to redact sensitive information)
Enhancement suggestions are welcome! When submitting an enhancement suggestion, please include:
- A clear and descriptive title
- A detailed explanation of the proposed functionality
- Any potential implementation details you can think of
- Why this enhancement would be useful to users
- Fork the repository
- Create a new branch from
main - Make your changes
- Run tests and ensure they pass
- Submit a pull request
- Follow the existing code style and conventions
- Update documentation if needed
- Add tests for new features
- Make sure all existing tests pass
- Keep your PR focused on a single topic
- Reference any relevant issues
-
Clone the repository:
git clone https://github.com/yourusername/freshrss-server.git cd freshrss-server -
Install dependencies:
npm install
-
Build the project:
npm run build
To test the server, you'll need:
- A running FreshRSS instance
- API credentials for that instance
Create a .env file in the root directory with:
FRESHRSS_API_URL=https://your-freshrss-instance.com
FRESHRSS_USERNAME=your-username
FRESHRSS_PASSWORD=your-password
We follow Conventional Commits specification:
feat:for new featuresfix:for bug fixesdocs:for documentation changesstyle:for formatting changes that don't affect code behaviorrefactor:for code changes that neither fix bugs nor add featurestest:for adding or modifying testschore:for routine tasks, maintenance, etc.
For example:
feat: add support for category filtering
fix: resolve connection timeout issue
docs: update installation instructions
Feel free to open an issue with your question, or reach out to the maintainers.
Thank you for your contributions!