# Contributing to MCP Environment & Installation Manager
We love your input! We want to make contributing to MCP Environment & Installation Manager as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
## Development Process
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request
## Pull Requests
1. Update the README.md with details of changes to the interface, if applicable.
2. Update the documentation with details of the new functionality.
3. The PR should work for the supported Node.js versions.
4. Include appropriate tests for your changes.
## Setting Up Development Environment
```bash
# Clone your fork
git clone https://github.com/YOUR-USERNAME/mcp-env-manager.git
# Install dependencies
cd mcp-env-manager
npm install
# Run in development mode
npm run dev
# Run tests
npm test
```
## Coding Style
- Follow the existing code style
- Use TypeScript for all code
- Include JSDoc comments for all functions and classes
- Keep files focused on a single responsibility
- Write unit tests for new functionality
## License
By contributing, you agree that your contributions will be licensed under the project's MIT License.