ansible-awx-mcp-connector

name	ansible-awx-mcp-connector
description	MCP connector for Ansible AWX/Tower – enables AI-powered playbook management, job execution, and infrastructure automation through Claude
license	Apache 2.0
tags	["cloud","automation","mcp","ansible","awx"]
difficulty	advanced
time_to_master	4-8 weeks
version	1.0.0

Ansible Awx MCP Connector

Overview

This skill enables Claude to interact with Ansible Awx through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Ansible Awx's REST API, allowing natural language control of Ansible Awx operations, intelligent automation, and AI-powered assistance for Ansible Awx workflows.

When to Use This Skill

• Playbook generation from natural language
• Job template creation and execution
• Inventory management and host organization
• Credential and secret management
• Workflow template design and orchestration

Architecture

┌─────────────┐     ┌─────────────────┐     ┌──────────────────┐
│   Claude     │────▶│   MCP Server    │────▶│   Ansible Awx      │
│   (Client)   │◀────│   (TypeScript)  │◀────│   (REST API      )│
└─────────────┘     └─────────────────┘     └──────────────────┘

Core Concepts

MCP Server Setup

The connector implements an MCP server that exposes Ansible Awx operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.

Key Endpoints/Interfaces

/api/v2/job_templates/, /api/v2/inventories/, /api/v2/projects/, /api/v2/credentials/, /api/v2/workflow_job_templates/

Implementation

// Ansible Awx MCP Server Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({
  name: "ansible-awx-mcp-connector",
  version: "1.0.0",
});

// Tool: List/Query Resources
server.tool(
  "list_resources",
  "List and query Ansible Awx resources with optional filters",
  {
    query: z.string().optional().describe("Search query or filter"),
    limit: z.number().optional().describe("Max results to return"),
  },
  async ({ query, limit }) => {
    // Call Ansible Awx REST API
    const response = await fetch(`${BASE_URL}/api/v2/job_templates/`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Tool: Create Resource
server.tool(
  "create_resource",
  "Create a new resource in Ansible Awx",
  {
    name: z.string().describe("Resource name"),
    config: z.object({}).passthrough().optional().describe("Resource configuration"),
  },
  async ({ name, config }) => {
    const response = await fetch(`${BASE_URL}/api/v2/job_templates/`, {
      method: "POST",
      headers: {
        "Authorization": `Bearer ${API_KEY}`,
        "Content-Type": "application/json",
      },
      body: JSON.stringify({ name, ...config }),
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: `Created: ${JSON.stringify(data)}` }],
    };
  }
);

// Tool: Analyze/Report
server.tool(
  "analyze",
  "AI-powered analysis of Ansible Awx data",
  {
    type: z.string().describe("Analysis type"),
    timeframe: z.string().optional().describe("Time range for analysis"),
  },
  async ({ type, timeframe }) => {
    // Fetch data and provide AI analysis
    const response = await fetch(`${BASE_URL}/api/v2/job_templates/`, {
      headers: { "Authorization": `Bearer ${API_KEY}` },
    });
    const data = await response.json();
    return {
      content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
    };
  }
);

// Start server
const transport = new StdioServerTransport();
await server.connect(transport);

Claude Desktop Configuration

{
  "mcpServers": {
    "ansible-awx-mcp-connector": {
      "command": "node",
      "args": ["path/to/ansible-awx-mcp-connector/index.js"],
      "env": {
        "ANSIBLE_AWX_API_KEY": "your-api-key",
        "ANSIBLE_AWX_BASE_URL": "https://your-instance-url"
      }
    }
  }
}

Best Practices

1. Authentication: Store API keys securely using environment variables; never hardcode credentials
2. Rate Limiting: Implement request throttling to respect Ansible Awx API rate limits
3. Error Handling: Provide clear, actionable error messages for common failure scenarios
4. Pagination: Handle paginated responses for large datasets efficiently
5. Caching: Cache frequently accessed read-only data to reduce API calls
6. Security: Validate all inputs before passing to the Ansible Awx API; sanitize outputs
7. Logging: Log all API interactions for debugging and audit purposes

Example Prompts

"Create a playbook to configure Nginx with SSL certificates on all web servers in the production inventory"

Security Considerations

• All API credentials must be stored as environment variables
• Implement input validation and sanitization for all tool parameters
• Use HTTPS for all API communications
• Follow the principle of least privilege for API token permissions
• Audit log all write operations for compliance tracking

Resources

• Ansible Awx Official Documentation
• MCP SDK Documentation: https://modelcontextprotocol.io
• MCP Server Examples: https://github.com/modelcontextprotocol/servers
• SkillGalaxy Repository: https://github.com/Sandeeprdy1729/skill_galaxy

Changelog

Version	Date	Changes
1.0.0	2026-04-01	Initial MCP connector skill

---

Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.