Thank you for your interest in contributing to CausalLayer! This document provides guidelines and information for contributors.
# Clone the repository
git clone https://github.com/smq9sn5jck-coder/causallayer-mcp.git
cd causallayer-mcp
# Install dependencies
npm install
# Run tests
npm test
# Start local development
npx wrangler dev- Use GitHub Issues
- Include steps to reproduce, expected vs actual behavior
- Include your environment (OS, Node.js version, Wrangler version)
- Check existing issues first
- Use the feature request template
- Describe the use case and expected behavior
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests (
npm test) - Commit with conventional commits (
feat:,fix:,docs:, etc.) - Push to your fork and open a PR
Check our roadmap issues for areas where contributions are especially welcome:
- 🌏 Jurisdiction modules — Add regulatory mappings for new countries/regions
- 🧪 Test scenarios — Industry-specific incident templates
- 📖 Documentation — Tutorials, integration guides, translations
- 🔌 Client integrations — Claude Desktop, Cursor, VS Code configurations
- 📊 Scoring models — New attribution algorithms and weighting schemes
- TypeScript strict mode
- ESLint + Prettier (run
npm run lint) - Meaningful variable names over comments
- Each MCP tool should be self-contained in its own module
We follow Conventional Commits:
feat: add Japanese jurisdiction module
fix: correct liability split rounding error
docs: add Claude Desktop integration guide
test: add edge case for multi-party incidents
chore: update wrangler to v4
By contributing, you agree that your contributions will be licensed under the MIT License.
- Open a Discussion
- Email: contributors@faultkey.com