Code Context Manager

# Contributing to Code Context Manager MCP Server Thank you for your interest in contributing to the Code Context Manager MCP Server! We welcome contributions from the community. ## Development Setup 1. Fork the repository 2. Clone your fork: ```bash git clone https://github.com/your-username/code-context-manager-mcp.git cd code-context-manager-mcp ``` 3. Set up the development environment: ```bash python -m venv venv source venv/bin/activate # Windows: venv\Scripts\activate pip install -r requirements.txt pip install esprima # For JS/TS support ``` 4. Start Redis for testing: ```bash docker run -d --name redis-stack -p 6379:6379 redis/redis-stack:latest ``` ## Testing Run the test suite: ```bash python test_search.py ``` Test MCP functionality with an MCP inspector/client. ## How to Contribute ### Reporting Issues - Use GitHub Issues to report bugs or request features - Provide detailed steps to reproduce bugs - Include your environment details (Python version, OS, etc.) ### Submitting Changes 1. Create a feature branch: `git checkout -b feature/your-feature-name` 2. Make your changes 3. Test thoroughly 4. Update documentation if needed 5. Commit with clear messages: `git commit -m "Add feature X"` 6. Push to your fork: `git push origin feature/your-feature-name` 7. Create a Pull Request ### Code Style - Follow PEP 8 for Python code - Use descriptive variable and function names - Add docstrings for new functions - Keep lines under 100 characters ### Types of Contributions - Bug fixes - New features - Documentation improvements - Performance optimizations - Additional language support ## Code of Conduct Please be respectful and constructive in all interactions. We aim to foster an inclusive and welcoming community. ## Questions? Feel free to open an issue for questions or join discussions in existing issues.