MCP.Market

Awx MCP server

by SurgeX-Labs·io.github.SurgeX-Labs/awx-mcp-server·v1.1.2·12 stars

Control AWX/Ansible Tower through natural language - 49 tools for automation

C66/100grade C
What users say
No reviews yet
Be the first
Safety scan
C66/100

full report

Adoption
New

12 stars

Reviews

Write one

Nobody has reviewed Awx yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Awx tools (50, 22 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • ansible_inventory

    List/show Ansible inventory hosts and groups using ansible-inventory. Use this when user asks to 'list inventory hosts', 'show inventory groups', 'display local inventory', 'what hosts are in my inventory file'.

  • ansible_playbookwrite action

    Execute/run an Ansible playbook locally for development and testing. Use this when user asks to 'run playbook locally', 'execute playbook', 'test playbook', 'dry-run playbook', or wants to run a playbook in their dev environment before pushing to AWX. Supports check mode (dry-run), extra vars, tags, and host limits.

  • ansible_rolewrite action

    Execute/run an Ansible role locally by generating a temporary playbook. Use this when user asks to 'run a role', 'execute role', 'test role locally', or wants to apply a specific role from their project without writing a full playbook.

  • ansible_taskwrite action

    Run an ad-hoc Ansible task/module locally. Use this when user asks to 'run ansible module', 'execute ad-hoc task', 'ping hosts', 'run shell command with ansible', 'test ansible module', or wants to run a single Ansible module without a playbook. Defaults to connection=local for localhost.

  • awx_credential_createwrite action

    Create AWX credential

  • awx_credential_deletewrite action

    Delete AWX credential

  • awx_credential_types_list

    List AWX credential types

  • awx_credentials_list

    List AWX credentials

  • awx_inventories_list

    List AWX inventories

  • awx_inventory_createwrite action

    Create AWX inventory

  • awx_inventory_deletewrite action

    Delete AWX inventory

  • awx_inventory_group_createwrite action

    Create group in AWX inventory

  • awx_inventory_group_deletewrite action

    Delete group from AWX inventory

  • awx_inventory_groups_list

    List groups in AWX inventory

  • awx_inventory_host_createwrite action

    Create host in AWX inventory

  • awx_inventory_host_deletewrite action

    Delete host from AWX inventory

  • awx_inventory_hosts_list

    List hosts in AWX inventory

  • awx_job_cancelwrite action

    Cancel/stop/abort a currently running AWX job execution. Use this when user asks to 'cancel job', 'stop job', 'abort job', 'kill job', or any request to halt a running job.

  • awx_job_deletewrite action

    Delete/remove an AWX job record from history. Use this when user asks to 'delete job', 'remove job', 'clean up job', or any request to permanently remove a job record.

  • awx_job_events

    Show/list/view/get detailed events, tasks, plays, and execution steps of an AWX job. Use this when user asks to 'show job events', 'view job tasks', 'list execution steps', 'see what tasks ran', 'show detailed job activity', 'view play-by-play execution', or any request about the individual task/play events within a job run. Can filter to show only failed events.

  • awx_job_failure_summary

    Analyze/diagnose/debug/troubleshoot why an AWX job failed and get actionable fix suggestions. Use this when user asks 'why did job fail', 'analyze failure', 'debug job error', 'show failure summary', 'what went wrong with job', 'diagnose job problem', 'troubleshoot job', or any request to understand and fix a failed job execution.

  • awx_job_get

    Get specific AWX job metadata and summary details including status, timing, template info, and playbook name. Use this to check a single job's current state, whether it succeeded or failed, and its start/finish times. Does NOT return console output or logs — use awx_job_stdout for that.

  • awx_job_launch

    Launch/execute/run/start a new AWX job from a template. Creates a new job execution instance.

  • awx_job_stdout

    Show/display/view/get the console output, stdout, logs, or terminal output of an AWX job execution. Use this when user asks to 'show job output', 'view job logs', 'display console output', 'get job stdout', 'show what the job printed', 'see the playbook output', 'show execution log', or any request to see the text/log output produced by a job run.

  • awx_jobs_list

    Show/list/display/view recent AWX jobs, job execution history, completed jobs, running jobs, failed jobs, job status, job runs, playbook executions. Use this when user asks to 'show recent jobs', 'list jobs', 'view jobs', 'get jobs', 'display job history', 'see recent activity', 'check job status', or any query about AWX job executions with timestamps and results.

  • awx_organization_get

    Get AWX organization by ID

  • awx_organizations_list

    List AWX organizations

  • awx_project_createwrite action

    Create AWX project

  • awx_project_deletewrite action

    Delete AWX project

  • awx_project_updatewrite action

    Update AWX project from SCM

  • awx_projects_list

    List AWX projects

  • awx_system_info

    Get AWX system information (config, dashboard, settings)

  • awx_template_createwrite action

    Create AWX job template

  • awx_template_deletewrite action

    Delete AWX job template

  • awx_templates_list

    List AWX job templates (NOT for recent jobs or job history). Templates are playbook definitions, configurations, settings. This shows available templates to run, not execution history or recent activity. For recent jobs/runs/executions, use awx_jobs_list instead.

  • create_playbookwrite action

    Create/write/generate an Ansible playbook YAML file locally. Use this when user asks to 'create a playbook', 'write a playbook', 'generate a playbook', 'make a new playbook', or wants to author Ansible YAML content before running it on AWX.

  • create_role_structurewrite action

    Scaffold/generate/create an Ansible role directory structure with standard subdirectories (tasks, handlers, templates, files, vars, defaults, meta). Use this when user asks to 'create a role', 'scaffold a role', 'generate role skeleton', 'init role structure', or wants to set up a new role from scratch.

  • env_get_active

    Get the currently active AWX environment

  • env_list

    List all configured AWX environments

  • env_set_active

    Set the active AWX environment

  • env_test_connection

    Test connection to an AWX environment

  • git_push_project

    Stage, commit, and push project changes to git remote (GitHub/GitLab). Use this when user asks to 'push to git', 'commit and push', 'push playbook changes', 'push project to github', 'publish changes'. After pushing, use awx_project_update to sync AWX.

  • list_playbooks

    List/show/display all Ansible playbooks in the workspace or project directory. Use this when user asks to 'list playbooks', 'show my playbooks', 'what playbooks exist', 'find playbooks'.

  • list_registered_projects

    List/show all registered local Ansible projects and the default. Use this when user asks to 'list my projects', 'show registered projects', 'what projects are configured'.

  • list_roles

    List/show/display all Ansible roles in the workspace. Use this when user asks to 'list roles', 'show my roles', 'what roles exist'.

  • project_playbooks

    Discover/find/list playbooks and roles under a registered project root. Use this when user asks to 'show project playbooks', 'find playbooks in project', 'discover playbooks', 'what playbooks does project have', 'list project roles'.

  • project_run_playbookwrite action

    Run a playbook using a registered project's inventory and environment. Use this when user asks to 'run project playbook', 'execute playbook from project', 'test project playbook locally'. Automatically uses the project's configured inventory.

  • register_project

    Register/add a local Ansible project directory for easy reuse. Use this when user asks to 'register project', 'add project', 'set up project', 'configure my ansible project'. Auto-detects git remote URL, inventory, and default playbook.

  • unregister_projectwrite action

    Remove/unregister a local Ansible project from the registry. Use when user asks to 'remove project', 'unregister project', 'delete project registration'.

  • validate_playbook

    Validate/check/lint Ansible playbook syntax using ansible-playbook --syntax-check. Use this when user asks to 'validate playbook', 'check playbook syntax', 'lint playbook', 'verify playbook', or wants to ensure a playbook is syntactically correct before running it.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings
  • Code scan25 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 217 days ago4/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 66/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Awx compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
66/100
higher than 23% of 48,255 servers
Tools
50
the typical server has 7
Tools that change things
44%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
12
more than 89% of 28,688 servers

What its tools let an agent do: 27 read · 3 create · 20 change

Install Awx in Claude Code, Cursor or VS Code

claude mcp add awx-mcp-server -- uvx awx-mcp-server
Add to Cursor

What the publisher says

From the Awx repository's README, as published. We do not edit it. Read it on GitHub

AWX MCP - AI-Powered AWX/AAP/Ansible Automation

Industry-standard MCP server for AWX/AAP/Ansible Tower automation

The AWX MCP Server connects AWX, Ansible Automation Platform (AAP), and Ansible Tower to AI tools, giving AI agents and assistants the ability to manage job templates, launch and monitor jobs, manage inventories and projects, and automate infrastructure workflows through natural language interactions.

Designed for developers who want to integrate their AI tools with AWX/AAP/Tower automation capabilities.

✨ Supports AWX (open source), AAP (Red Hat), and Ansible Tower (legacy) - same API, same features!

🎯 Usage Patterns

Primary: MCP Server (Industry Standard) ⭐ RECOMMENDED

Standard MCP implementation using STDIO transport (like Postman MCP, Claude MCP)

Use Case: AI assistants (GitHub Copilot, Claude, Cursor) + AWX automation

Features:

  • ✅ Works with any MCP client (Copilot, Claude, Cursor, Windsurf, etc.)
  • ✅ Industry standard pattern (STDIO transport)
  • ✅ Simple installation: pip install git+https://github.com/USERNAME/awx-mcp-server.git
  • ✅ Portable across all MCP-compatible tools
  • ✅ 18+ AWX operations (templates, jobs, projects, inventories)

Best For: AI-powered automation, natural language AWX control, any MCP client

Optional: VS Code Extension (UI Enhancement)

Optional UI features for VS Code users

Use Case: VS Code users who want additional UI (sidebar views, tree providers)

Features:

  • ✅ Sidebar with AWX instances, jobs, metrics
  • ✅ Tree view of AWX resources
  • ✅ Configuration webview
  • ✅ Auto-configures MCP (or respects manual setup)

Best For: VS Code users wanting rich UI alongside MCP functionality

🚀 Quick Start

Installation Methods

You have three ways to install and run the AWX MCP Server:

→ For customization and running from your own repository, see INSTALLFROMSOURCE.md

Option 1: PyPI Installation (Recommended for Quick Start)

Install from PyPI

# Install the MCP server
pip install awx-mcp-server

# Verify installation
python -m awx_mcp_server --version

Configure for VS Code

Edit VS Code settings.json (Ctrl+, → Search "chat.mcp"):

{
  "mcpServers": {
    "awx": {
      "command": "python",
      "args": ["-m", "awx_mcp_server"],
      "env": {
        "AWX_BASE_URL": "https://your-awx.com"
      },
      "secrets": {
        "AWX_TOKEN": "your-awx-token"
      }
    }
  }
}

Restart VS Code and the MCP server will be available in Copilot Chat.

Option 2: Install from Source (For Customization)

Perfect for: Forking, customization, enterprise deployments, contributing

Quick install:

# Clone the repository (or your fork)
git clone https://github.com/SurgeX-Labs/awx-mcp-server.git
cd awx-mcp-server/awx-mcp-python/server

# Create virtual environment
python -m venv venv
source venv/bin/activate  # Windows: .\venv\Scripts\Activate.ps1

# Install in editable mode
pip install -e .

# Verify
python -m awx_mcp_server --version

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Awx: common questions

Is Awx MCP server safe?
With care: it is graded C, so read the findings first (66/100). Read the Awx safety report
How do I install Awx?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Awx need an API key?
Yes. The registry entry asks for AWX_TOKEN, AWX_PASSWORD.
Is Awx maintained?
The last commit was 254 days ago (2026-02-23). The latest release is v1.1.2.
How does Awx compare with other MCP servers?
safety score 66/100 (higher than 23% of 48,255 servers); tools 50 (the typical server has 7); tools that change things 44% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.