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:
uv tool install ansible-mcp
Then configure your client in one command:
GitHub Copilot in VS Code
ansible-mcp install --client copilot
Claude Code
ansible-mcp install --client claude
Cursor
ansible-mcp install --client cursor
For project-scoped setup (checked into your repo):
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+Cto stop it when running manually. - In real usage, the client launches and manages this process for you.
Tool coverage
Core Ansible operations
lintplaybook_syntax_checkplaybook_runinventory_parseinventory_graph
Upstream-compatible endpoints
list_available_toolszen_of_ansibleansible_content_best_practicesansible_lintade_environment_infoade_setup_environmentadt_check_envansible_create_playbookansible_create_collectiondefine_and_build_execution_envansible_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 verbose metadata payloads | Compact tool descriptions and bounded responses |
| Docs access | Mostly extension context | MCP resources (ansible://docs/*) |
Marketplace compatibility
For Marketplace specifics and how to ship a VS Code wrapper extension around this server, see docs/MARKETPLACE_COMPATIBILITY.md.
Additional docs
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for ansible-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ansible_mcp-1.0.1.tar.gz | 27.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ansible_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.5 kB
Release files / ansible_mcp-1.0.1.tar.gz
| Download URL | ansible_mcp-1.0.1.tar.gz |
|---|---|
| Size | 27.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6e9a3943a2e35c323518d6e9d56154684f51b4484873f3ea95f2ec6f7376462
|
|
BLAKE2b-256 checksum How to use checksums |
fe705d90c4da3cd669a55b4ea295d70288e594d88f580bcda9807a47e45bbedc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 14, 2026.
Transparency logRelease files / ansible_mcp-1.0.1-py3-none-any.whl
| Download URL | ansible_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 34.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8906f752d49c3770aaed7a4aadb626a5dd6a66d06beaeeed6c9cbfcc83e0b266
|
|
BLAKE2b-256 checksum How to use checksums |
a77485fdc348543f271c30935b1a29e5d71e9375cdbfa3a385ac934c964ad011
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 14, 2026.
Transparency logSecurity for ansible-mcp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ansible_mcp-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
