Releases
All components follow Semantic Versioning: a major version can break compatibility, a minor version adds features, a patch
version fixes bugs. Each repository has its own CHANGELOG.md; images are on ghcr.io/aiwcorpo only.
Current versions
Section titled “Current versions”| Component | Version | Image or package | Changes |
|---|---|---|---|
| Gateway | 2.0.1 | ghcr.io/aiwcorpo/mcp-gateway |
CHANGELOG |
| Credential broker | 2.0.0 | ghcr.io/aiwcorpo/mcp-credential-broker |
CHANGELOG |
| Portal | 2.0.1 | ghcr.io/aiwcorpo/mcp-portal |
CHANGELOG |
| MCP servers: GitLab, Jira, Confluence, OpenSearch, service desk | 2.0.0 | ghcr.io/aiwcorpo/mcp-server-<system> |
CHANGELOG in each mcp-server-<system> repository |
| REST adapter server | 2.0.0 | ghcr.io/aiwcorpo/mcp-server-adapter |
CHANGELOG |
| Contracts | 7.0.0 | Maven Central and npm @aiwcorpo/mcp-contracts |
CHANGELOG |
| Server starter library | 4.0.0 | Maven Central | CHANGELOG |
| Server template | 2.0.0 | GitHub template repository | CHANGELOG |
The mcp-platform Compose bundle defaults to the versions above. Offline packages are on
mcp-platform-offline releases: platform v2.0.1, servers v2.0.0.
Compatibility
Section titled “Compatibility”- Gateway, broker and portal 2.x use contracts 7.0.0 and work only with each other; none of them works with a 1.x component.
- MCP servers 2.x need a gateway 2.x. A 1.x server refuses to start while a 1.x setting is left in its environment file.
- Claude Code with MCP 2026-07-28 needs gateway 2.0.1 or newer: 2.0.0 left out
ttlMsandcacheScopein the tool list and the client showed no tools.
Upgrading
Section titled “Upgrading”Deploy the broker and the gateway before the portal. Steps for each version: Upgrade.