Semaphore Open Source 1.6: MCP Server, sem-ai Out of the Box, and Partial Job Reruns

    The MCP server and sem-ai are coming to Semaphore open source. Version 1.6 arrives exactly one year after 1.5 and packages up around 494 pull requests of new capabilities, built over the past year and now shared with the community.

    What Shipped

    MCP server in the open source editions

    The MCP server is now included in both the Community Edition and the Enterprise Edition of Semaphore open source. It’s part of a broader push this year to bring AI and automation tools into Semaphore.

    sem-ai works out of the box

    sem-ai is fully supported with no additional configuration necessary. It works with both service accounts and user tokens.

    New public API endpoints

    There are a lot of new public API endpoints, including endpoints for artifacts and for pre-flight checks in the Enterprise Edition. Artifacts are now supported through the REST API. The result: almost everything in Semaphore is now configurable from the API, either through sem-ai or through the regular API endpoints.

    Partial job reruns

    Long and complex pipelines no longer need a full rerun. With partial job reruns, not everything needs to be rerun now.

    New filtering options in the UI

    The UI gets new filtering options.

    RustFS replaces MinIO for artifact storage

    Semaphore previously used MinIO as its artifact storage engine. With MinIO moving away from the open source community, we switched to RustFS as the replacement. RustFS also powers our tests.

    Security fixes and improvements

    The release also includes a lot of security fixes and general improvements.

    What’s Coming

    The release candidate will be ready in the next couple of days, and it will include the extended changelog with the full list of changes.

    As always, we accept PRs from the community. If you have comments or suggestions, open an issue or a PR on the Semaphore repository. All contributions and feedback are very welcome.

    Want to discuss this article? Join our Discord.

    Pete Miloravac
    Writen by:
    Pete Miloravac is a software engineer and educator at Semaphore. He writes about CI/CD best practices, test automation, reproducible builds, and practical ways to help teams ship software faster and more reliably.
    Star us on GitHub