Contributing to CrowdSentinel MCP Server

Contributing to CrowdSentinel MCP Server

Thank you for your interest in contributing to the CrowdSentinel MCP Server! CrowdSentinel is an AI-powered threat hunting and incident response MCP server featuring 79+ tools, 6,060+ detection rules, and baseline behaviour analysis. All kinds of contributions are welcome.

Bug reports

If you think you've found a bug in the CrowdSentinel MCP Server, we welcome your report. It's very helpful if you can provide steps to reproduce the bug, as it makes it easier to identify and fix the issue.

Feature requests

If you find yourself wishing for a feature that doesn't exist in the CrowdSentinel MCP Server, you are probably not alone. Please do not hesitate to open an issue which describes the feature you would like to see, why you need it, and how it should work.

Pull requests

If you have a fix or a new feature, we welcome your pull requests. You can follow the following steps:

1. Fork your own copy of the repository to your GitHub account by clicking on `Fork` button on [CrowdSentinel's GitHub repository](https://github.com/thomasxm/CrowdSentinels-AI-MCP).

2. Clone the forked repository on your local setup.

   git clone https://github.com/$user/CrowdSentinels-AI-MCP

   Add a remote upstream to track upstream `CrowdSentinels-AI-MCP` repository.

   git remote add upstream https://github.com/thomasxm/CrowdSentinels-AI-MCP

3. Create a topic branch.

   git checkout -b 

4. Make changes and commit it locally.

   git add 
   git commit

Commit messages could help reviewers better understand what the purpose of the submitted PR is. They could help accelerate the code review procedure as well. We encourage contributors to use **EXPLICIT** commit messages rather than ambiguous ones. In general, we advocate the following commit message types:

• Features: commit message starts with feat, for example: "feat: add user authentication module"
• Bug Fixes: commit message starts with fix, for example: "fix: resolve null pointer exception in user service"
• Documentation: commit message starts with doc, for example: "doc: update API documentation for user endpoints"
• Performance: commit message starts with perf, for example: "perf: optimise the performance of user service"
• Refactor: commit message starts with refactor, for example: "refactor: reorganise user service to improve code readability"
• Test: commit message starts with test, for example: "test: add unit test for user service"
• Chore: commit message starts with chore, for example: "chore: update dependencies"
• Style: commit message starts with style, for example: "style: format the code in user service"
• Revert: commit message starts with revert, for example: "revert: revert the changes in user service"
• CI/CD: commit message starts with ci, for example: "ci: update GitHub Actions workflow for Python 3.13 supp