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-devtools-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-devtools-mcp Standalone, vendor-agnostic MCP server for Ansible workflows with first-class support for modern MCP clients (GitHub Copilot, Claude Code, Cursor). ## Requirements - Python 3.12+ - `ansible-core` 2.20+ (installed automatically as a package dependency) - `uv` recommended for install and execution ## One-click setup Install once: ```bash uv tool install ansible-devtools-mcp ``` Then configure your client in one command: ### GitHub Copilot in VS Code ```bash ansible-devtools-mcp install --client copilot ``` ### Claude Code ```bash ansible-devtools-mcp install --client claude ``` ### Cursor ```bash ansible-devtools-mcp install --client cursor ``` For project-scoped setup (checked into your repo): ```bash ansible-devtools-mcp install --client copilot --scope project --workspace-root . ansible-devtools-mcp install --client cursor --scope project --workspace-root . ``` Use a custom server key in client config if needed: ```bash ansible-devtools-mcp install --client copilot --name ansible-devtools-mcp-prod ``` ## Running the server manually Default transport (STDIO): ```bash ansible-devtools-mcp serve --stdio ``` Streamable HTTP transport: ```bash ansible-devtools-mcp serve --http --host 127.0.0.1 --port 8000 ``` SSE transport: ```bash ansible-devtools-mcp serve --sse --host 127.0.0.1 --port 8000 ``` ## Why `ansible-devtools-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` -…
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.