Standalone, vendor-agnostic MCP server for Ansible tooling
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-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-mcp Standalone MCP server for Ansible workflows with first-class support for modern MCP clients (GitHub Copilot, Claude Code, Cursor). ## One-click setup Install once: ```bash uv tool install ansible-mcp ``` Then configure your client in one command: ### GitHub Copilot in VS Code ```bash ansible-mcp install --client copilot ``` ### Claude Code ```bash ansible-mcp install --client claude ``` ### Cursor ```bash ansible-mcp install --client cursor ``` For project-scoped setup (checked into your repo): ```bash ansible-mcp install --client copilot --scope project --workspace-root . ansible-mcp install --client cursor --scope project --workspace-root . ``` ## Why `ansible-mcp serve --stdio` keeps the terminal open `--stdio` runs a long-lived MCP server process. It waits for JSON-RPC messages from your MCP client. - This is expected. - Press `Ctrl+C` to stop it when running manually. - In real usage, the client launches and manages this process for you. ## Tool coverage ### Core Ansible operations - `lint` - `playbook_syntax_check` - `playbook_run` - `inventory_parse` - `inventory_graph` ### Upstream-compatible endpoints - `list_available_tools` - `zen_of_ansible` - `ansible_content_best_practices` - `ansible_lint` - `ade_environment_info` - `ade_setup_environment` - `adt_check_env` - `ansible_create_playbook` - `ansible_create_collection` - `define_and_build_execution_env` - `ansible_navigator` Detailed parity notes: `ansible://docs/upstream-parity` ## Upstream comparison | Area | VS Code Ansible MCP (extension-coupled model) | ansible-mcp | |---|---|---| | Packaging | Coupled to extension/monorepo workflows | Standalone Python package (`ansible-mcp`) | | Client scope | Primarily VS Code/Copilot flows | Any MCP-compatible client | | Transport | Usually extension-managed STDIO | STDIO, Streamable HTTP, SSE | | Tool architecture | Extension-shaped integration | Plugin router + entry-point extension model | | Token behavior | Often more ver…
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.