Semaphore Uncut

We’re preparing a new update for the Semaphore MCP server that will make it easier for developers to connect AI agents and developer tools.

The focus of this update is authentication.

Today, connecting an agent to the MCP server typically requires using a long-lived API token. While this works well, it also means developers need to generate credentials, store them in configuration files, and manage them manually.

In our next release, coming next week, we’re introducing OAuth authentication support for the MCP server.

This will make connecting agents and developer tools significantly simpler.

Instead of generating and storing API tokens, developers will be able to authenticate through a familiar OAuth flow. When configuring an agent, a browser window opens, you log in, and approve access to the MCP server. Once approved, the connection is established automatically.

This approach removes the need to manage long-lived credentials and makes integrations easier to set up.

It also improves compatibility with modern agentic development tools. Some tools have limitations when working with static API tokens, and OAuth removes those barriers.

Read more on our blog.

Pete Miloravac

The Semaphore Team

https://semaphore.io

🚀 We’re introducing AI-driven onboarding and workflow automation in Semaphore. Our new assistive agent helps teams generate pipeline configurations, understand failed jobs, re-run workflows, and refine CI/CD setups using natural language — all while keeping developers fully in control. This is the beginning of Agent-Driven Semaphore: CI/CD at the core, AI handling the repetitive work. Watch to see what’s coming next.

Give Semaphore a spin:https://semaphore.io/

Over the past few weeks, we’ve been refining our roadmap for 2026 and focusing on where Semaphore can deliver the most value.

Our direction is clear: extend CI/CD beyond execution — and help developers ship software faster.

Here’s what’s coming next.

In this episode of Semaphore Uncut, Malcolm Matalka (Terrateam) discusses GitOps, Terraform tooling, OpenTofu workflows, and building developer tools that stay invisible.

In this episode of Semaphore Uncut, Jamie Dobson, co-founder and former CEO of Container Solutions, shares a thoughtful perspective on generative AI, developer productivity, and system stability.

The conversation explores why recent research shows engineers feeling happier and more productive with AI tools—while system reliability quietly declines. Jamie explains how AI-generated code can appear correct while introducing subtle long-term risk, and why speed without deep understanding can be dangerous for growing systems.

They also discuss why looking back at the history of computing—from time-sharing to early neural networks—helps demystify today’s AI hype. The episode closes with a reflection on the stories we tell about technology, how humans and machines can work together, and what engineering leaders should be paying attention to next.

👉 Read the full blog post for the complete conversation — and happy listening!

In this episode of Semaphore Uncut, Sebastian Gierlinger, VP of Engineering at Storyblok, shares what it really takes to scale a fully remote engineering organization—from early startup days to a 250-person company.

The conversation explores how Storyblok scaled engineering across multiple time zones without losing alignment or delivery speed. Sebastian explains why Scrum stopped working as the team grew, what changed after adopting Shape Up, and how specialization—if left unchecked—can quietly turn into a bottleneck for growing teams.

They also discuss what remote-first organizations need to get right as they scale, from decision-making and trust to execution at speed. The episode closes with a candid look at how AI is already changing day-to-day engineering work—and why scaling engineering is ultimately less about hiring faster and more about designing better systems.

👉 Read the full blog post for the complete conversation — and happy listening!

In this episode of Semaphore Uncut, Keren Fanan (CEO & Co-founder) and Hadar Geva (CTO & Co-founder) of MyOp share how years of building and scaling frontend systems led them to rethink how UI should be built, shipped, and managed in production.

This conversation covers:

* How frontend systems break down over time due to framework churn and legacy code

* Why treating UI components as runtime contracts changes how teams ship and experiment

* How MyOp enables safe UI rollouts and gradual frontend modernization without redeployments

* Where this approach goes beyond traditional micro-frontend architectures

* How AI-generated UI is accelerating the need for more flexible frontend systems

* What MyOp’s open, framework-agnostic model looks like in practice

A clear, practical look at how frontend architecture is evolving—and what it means for teams building long-lived products.

👉 Read the full blog post for the complete conversation — and happy listening!

AI agents can reason, but they don’t actually understand your systems. MCP servers fix that by giving your copilots and assistants structured access to your tools, APIs, and CI/CD data. And the best part is that building one is much simpler than most people expect.

In the latest episode of Technical Tips, Tommy walks through how to create a functional MCP server in just a few minutes. He connects it to Semaphore’s API, pulls real project data, and shows how to expose those insights to tools like OpenAI Codex. It’s a straightforward, hands-on demo that finally makes MCP feel practical instead of theoretical.

If you’ve been curious about MCP or you’re trying to make your AI tools genuinely useful in day-to-day engineering work, this is the perfect place to start. You’ll see how an MCP server communicates with AI clients, how to wrap a real API into it, how to test everything using the MCP Inspector, and how easily you can turn your CI/CD workflows into a conversational experience.

By the end, you’ll understand how surprisingly little code it takes to give your AI agents real operational awareness.

Access the full guide on our blog.

In this episode of Semaphore Uncut, Jonathan Reimer—founder of Crowd.dev and now VP of Outbound Products at the Linux Foundation—breaks down what he’s learned from years inside the open source startup ecosystem.This conversation covers:

* How Crowd.dev grew into a core insights platform for OSS communities and was later acquired by the Linux Foundation

* The three types of open source companies Jonathan identified after speaking with 400–500 founders

* Why GitHub stars are vanity metrics—and which signal actually reflects real adoption

* When open source provides a real go-to-market edge, and when it doesn’t

* How AI is already influencing OSS development, from automated bug fixes to running LLMs locally

* Why open source models may ultimately dominate the model layer as costs fall

A sharp, fast overview of the forces shaping developer tools, open source ecosystems, and AI infrastructure today.

👉 Read the full blog post for the complete conversation — and happy listening!

In this episode of Technical Tips, Tommy shows you how to run tests across multiple environments without duplicating your CI/CD setup or writing repetitive jobs.He explains how job matrices in Semaphore help you expand test coverage, catch regressions early, and keep your pipelines organized and efficient.

You can also check out the blog post Job Matrix: Feature Showcase for a detailed walkthrough with examples in both the Workflow Editor and YAML.

Happy building,

The Semaphore Team