Skip to content

v0.1.0 — Give agents Ansible. Not the keys.

Choose a tag to compare

View all tags
@real-limitless real-limitless released this 09 Aug 19:38
· 20 commits to main since this release
v0.1
8ab6f03

AI can run your fleet. It should not own your fleet.

ansible-flow-mcp is now public.

It lets AI assistants use Ansible the way a careful operator would — with guardrails — so automation moves faster without handing the model the keys to production.

Hero

The problem leaders already feel

AI coding tools are excellent at suggesting work. The moment they can execute across servers, three things go wrong:

  1. Too much power — one compromised session or a bad prompt becomes a path across the estate
  2. No clear perimeter — every machine starts to look like a control plane
  3. No safe default — “just run it” beats “preview the change first”

That is not a tooling gap. It is a governance gap.

Why this exists

What this product is

A bridge between AI agents and the automation you already trust (Ansible) — designed so:

  • Agents work through a single, controlled entry point
  • Machines only become targets after they are explicitly enrolled
  • Changes prefer preview first, apply second
  • Dangerous freestyle execution is refused by design, not by hope

Think of it as: the AI gets a disciplined runbook seat — not root on every host.

Two ideas, one story

For the agent: a disciplined loop

Discover the right capability → understand the inputs → dry-run → only then change the world.

Agent loop

For the fleet: one bastion, enrolled workers

The AI talks to the hub. The hub reaches machines over the path ops already understands. Workers do not become a hop plane for lateral movement.

Hub and spokes

Old instinct This release
“Give the model the control node” Give the model a governed seat
“Any host can be the brain” One hub. Everything else is enrolled
“Mesh everything” Bastion model you can explain to security
“Trust the prompt” Policy and topology refuse the bad ask

Who it is for

  • Platform / SRE leaders who want AI in the loop without a new mesh OS
  • Security-minded CTOs who need a story: entry point, enrollment, least privilege
  • Teams already on Ansible who refuse to throw away that investment for a chatbot

Operators keep a simple day-two surface — inventory, groups, invites, hand-off to the AI client.

Operators

Why this first release matters

This is not a demo wrapper around a shell.

It is the first version of a product thesis:

Agents should accelerate operations.
They should not redefine your trust boundary.

v0.1.0 ships that thesis as installable software — open source, Apache-2.0, on PyPI.

Try it

pip install ansible-flow-mcp

Product story and visuals: README
How the fleet model works: Hub guide
Threat model: Security

Part of the same long game as OpenFlow — agentic automation with a real control plane, not vibes.

Not affiliated with Red Hat or the Ansible project beyond use of the public tools and documentation.

Assets 2
Loading