MCP server exposing Ansible modules to AI agents (search → schema → check → execute)
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ansible-flow-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ansible-flow-mcp **Give agents Ansible. Not the keys.** MCP server that exposes real Ansible modules and playbooks to AI agents — and a **SSH hub/spoke fabric** so multi-host automation is enrolled, bastion-scoped, and check-first by default.  | Track | What you get | | --- | --- | | **Agent loop** | `search → schema → check → execute` on allowlisted collections | | **Fleet fabric** | One hub · join tokens · SSH ForceCommand spokes · fixed inventory | [OpenFlow dual-track](https://github.com/real-limitless/OpenFlow) · [Marketing site](site/) · [Campaign storyboard](docs/campaign/) · [Hub/spoke ops](docs/HUB.md) · Apache-2.0 Not affiliated with Red Hat or the Ansible project beyond using the public Ansible CLI and docs. **New here?** **[Marketing site](site/)** (story + Schema Lab) · full step-by-step **[docs/QUICKSTART.md](docs/QUICKSTART.md)** — local MCP · compose lab · bare-metal hub/spoke · editor wiring. ```bash ./scripts/site_preview.sh # http://127.0.0.1:8765/ (gallery + live schemas) ``` --- ## Visual tour | | | | :---: | :---: | | **Why it exists** | **Agent loop** | |  |  | | **Hub / spoke fabric** | **Operators** | |  |  | Screenshots live in [`docs/images/campaign-*.png`](docs/images/). Re-shoot from [`docs/campaign/`](docs/campaign/) with `./capture.sh`. --- ## Why this exists Agents on a god-mode control node invent inventory, reach for `shell`, and treat every worker as an entrypoint. That is not a security model.  **You need this when:** - You want Cursor …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.