Contributing to fme-mcp
Thank you for your interest in contributing to fme-mcp! We welcome contributions from geospatial specialists, software engineers, security researchers, and data practitioners worldwide.
Code Standards & Guidelines
- Code & Comments: Please write documentation, commit messages, and docstrings in clear English.
- Type Annotations: Python code should be type-hinted and pass
mypy. - Linting & Formatting: We use
rufffor formatting and linting. - Testing: Add unit tests in
tests/unit/for new tools and fixes. - Security: Validate inputs using the existing path and command security guards.
Development Workflow
- Fork the repository on GitHub:
https://github.com/mwjouini/fme-mcp. - Clone your fork locally:
- Install dependencies in an isolated virtual environment:
- Run the automated test suite:
- Create a descriptive feature branch:
- Commit changes with Conventional Commits (e.g.
feat(spatial): add DBSCAN clustering tool). - Push to your branch and submit a Pull Request against
main.