# Contributing to MCP Codebase Insight
> 🚧 **Documentation In Progress**
>
> This documentation is being actively developed. More details will be added soon.
## Getting Started
1. Fork the repository
2. Clone your fork
3. Create a new branch
4. Make your changes
5. Submit a pull request
## Development Setup
See the [Development Guide](docs/development/README.md) for detailed setup instructions.
## Code Style
- Follow PEP 8 guidelines
- Use type hints
- Write docstrings for all public functions and classes
- Keep functions focused and small
- Write clear commit messages
## Testing
- Write tests for new features
- Ensure all tests pass before submitting PR
- Include both unit and integration tests
- Document test cases
## Documentation
- Update documentation for new features
- Follow the documentation style guide
- Include examples where appropriate
- Keep documentation up to date with code
## Pull Request Process
1. Update documentation
2. Add tests
3. Update CHANGELOG.md
4. Submit PR with clear description
5. Address review comments
## Code of Conduct
Please note that this project is released with a [Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tosin2013/mcp-codebase-insight'
If you have feedback or need assistance with the MCP directory API, please join our Discord server