Summary

Change project license from MIT to Apache 2.0 for improved patent protection and clearer contributor terms.

Rationale

Apache 2.0 is fully compatible with MIT - MIT-licensed code can be included in Apache 2.0 projects with proper attribution.

Required Changes

1. Create NOTICE file

GitLab MCP Server
Copyright 2025-present SW Foundation

This product includes software originally developed by:
- zereight (https://github.com/zereight/gitlab-mcp)
- Contributors to the original gitlab-mcp project

The original software was released under the MIT License.

2. Update LICENSE file

Replace MIT license text with Apache 2.0 license text. Copyright holder: SW Foundation

3. Preserve original MIT license

Create LICENSE.MIT file containing the original MIT license for reference and attribution compliance.

4. Update package.json

"license": "Apache-2.0"

5. Update README.md

• Change license badge to Apache 2.0
• Update license section to reference Apache 2.0
• Add note about original MIT-licensed code attribution

6. Update any license headers in source files (if present)

Ensure consistency across codebase.

Implementation Checklist

• Create NOTICE file with attribution (copyright: SW Foundation)
• Create LICENSE.MIT (preserve original)
• Replace LICENSE content with Apache 2.0 (copyright: SW Foundation)
• Update package.json license field
• Update README.md license references
• Verify npm package metadata after publish

Acceptance Criteria

• LICENSE contains Apache 2.0 text with SW Foundation copyright
• NOTICE properly attributes original authors
• LICENSE.MIT preserved for reference
• package.json shows Apache-2.0
• README reflects new license
• npm registry shows correct license after next release

Priority

Low - Legal/administrative change, no functional impact.