Steampunk Spotter

Red Hat Connect London 2026: See Spotter MCP Check AI-Written Code Live

September 30, 2026 - Words by  The Spotter Team - 4 min read

Card image caption

XLAB Steampunk is coming to Red Hat Connect London on October 8, 2026! Meet us at booth #6 to see how to govern your Ansible and Terraform code, whether an engineer or an AI agent wrote it. We’ll reveal Spotter MCP, which lets an AI coding agent check its own code with Steampunk Spotter as it writes it, and we’ll run it live.

If your team is using more AI in automation work and wants to keep standards consistent, come and talk to us. We’ll walk you through it with your own stack in mind.


Why the policy check is moving closer to the code

AI assistants have changed how quickly automation gets written. A task that used to take an afternoon of writing and testing a Playbook now takes a prompt and a few minutes. The code usually looks right, so it’s easy to approve without a closer look. That’s how ungoverned automation reaches production.

Steampunk Spotter is the shift-left governance layer for Ansible and Terraform code. It checks every change against your policy before it runs, whether an engineer, a third-party collection or an AI agent wrote it.


See how Spotter MCP checks AI-written code live

Spotter now connects directly to AI coding agents through Spotter MCP. Here’s what that changes for your team.

Before Spotter MCP: An engineer writes a Playbook or gets one from an AI assistant. Then they run a Spotter scan, read the results and fix the code by hand. Checking is a separate step, and it only happens if someone remembers to do it.

With Spotter MCP: The AI agent does all of this itself. Once your team installs the Spotter Agent Plugin, the agent checks every Playbook or Terraform configuration it writes against your policy. It fixes what Spotter finds and checks again, so your team gets code that already follows your rules.

At the booth, we’ll show this live. We’ll give an AI agent an everyday automation task, and you’ll see it write the code, check it with Spotter, fix what Spotter finds and end up with a clean result.

Spotter MCP works with AI coding tools including Claude Code, GitHub Copilot and Devin AI (Windsurf), so your team can keep the tools it already uses. For the kinds of mistakes Spotter catches in AI-written code, such as hallucinated modules and deprecated syntax, see AI-Generated Ansible Playbooks: Where AI Helps and Where It Breaks .


Define, validate and enforce your standards

We’ll also show you how teams use Spotter to define their automation standards as policy-as-code, validate Ansible Playbooks and Terraform configurations against them, and enforce compliance policies. Enforcement happens at the points where it counts, whether that’s a developer’s editor, a pull request or a pre-execution check in AAP.


Tell us how your team uses AI, and win a prize

We want to hear how your team uses AI in automation work, including which tools you like and where they fall short. Stop by, share your experience, and you’ll be entered into our raffle.


See you in London

No two automation environments look the same. Spotter runs as SaaS, on-prem or air-gapped, and we can tailor custom features to your setup. Bring your questions about your pipelines, policies or upgrade plans, and we’ll help you figure out what governance should look like for your team.

Stop by booth #6 on October 8 for a live demo, a chat about your automation setup, or just to tell us which AI tools your team can’t work without. And if you’d like dedicated time for a deeper dive into your automation challenges, book a meeting with our experts in advance.


Frequently Asked Questions

How can I check AI-generated Ansible and Terraform code? You can check AI-generated Ansible and Terraform code by validating it against your policy before it runs. Steampunk Spotter does this for every change, and with Spotter MCP, the AI agent runs the check itself while it writes the code. It fixes what Spotter finds before your team reviews it.

What is Spotter MCP? Spotter MCP connects AI coding agents directly to Steampunk Spotter through the Model Context Protocol (MCP), the standard way AI agents connect to external tools. Once your team installs the Spotter Agent Plugin, the agent checks the Ansible Playbooks and Terraform configurations it writes against your policy. It fixes what Spotter finds and checks again, without anyone having to run a scan.

Does Spotter replace Red Hat Ansible Automation Platform? No, Spotter doesn’t replace Red Hat Ansible Automation Platform (AAP). Spotter checks your automation code before it runs, while AAP runs it. The two work together, and Spotter can check code as a pre-execution step in AAP.

Found this post useful?

Get our monthly newsletter.

Thank you for subscribing!

Please wait

Processing, please wait...

Keep up with what we do on our social media.