MCP Server for Ansible Automation Platform: Traditional vs AI-Driven Automation

The MCP (Model Context Protocol) server for AAP transforms how users interact with Ansible Automation Platform — from clicking through multiple UI screens to simply describing what they need in natural language.

Traditional Automation Workflow (4 Steps)

Without MCP, launching automation requires navigating the AAP UI manually:

Step 1: Navigate to AAP Open the AAP web interface and log in.

Step 2: Find the correct job template Browse or search through potentially hundreds of job templates and workflow templates to find the right one.

Step 3: Fill out survey fields Complete the job template survey with required parameters (hostnames, variables, options).

Step 4: Submit and kick off automation Review and launch the job, then monitor execution.

This works, but requires knowledge of which template to use, what parameters to fill in, and familiarity with the AAP interface.

See also: Top AI Models: ChatGPT, Claude, Gemini, LLaMA in Communication

AI-Driven Automation with MCP Server (2 Steps)

With the AAP MCP server, the same task becomes a conversation:

Step 1: Navigate to AI chat interface Open any MCP-compatible AI assistant — ChatGPT, Claude, Cursor, or others.

Step 2: Describe what you need Tell the AI what you want in natural language. The AI uses the MCP server to: • Find the correct job template • Determine required parameters • Request additional information if needed • Launch the automation • Report results

Example Conversation

User: "Request a developer VM with 8GB RAM running RHEL 9"
AI Assistant: I found the "Provision Developer VM" job template. 
I need a few more details:
- Which datacenter? (us-east, us-west, eu-central)
- SSH key to inject?
- Any additional software packages?
User: "us-west, use my default key, add podman and vim"
AI Assistant: ✅ Job launched successfully (Job #4521)
  - Template: Provision Developer VM
  - Host: dev-vm-0847.us-west.example.com
  - Status: Running
  You can verify results in AAP.

How It Works

┌─────────────┐     MCP Protocol     ┌─────────────┐
│  AI Client   │◄───────────────────►│  AAP MCP     │
│  (ChatGPT,   │                     │  Server      │
│   Claude,    │                     │              │
│   Cursor)    │                     └──────┬───────┘
└─────────────┘                             │
                                            │ API
                                            ▼
                                    ┌───────────────┐
                                    │  Ansible       │
                                    │  Automation    │
                                    │  Platform      │
                                    └───────────────┘

The MCP server exposes AAP capabilities (job templates, inventories, credentials) as MCP tools that any compatible AI client can discover and use.

See also: Ansible Development Tools MCP Server: Use Claude Code, Cursor, Copilot, and Gemini for Ansible Development

Technology Preview Status

The MCP server for AAP is a Technology Preview with AAP 2.7 (GA June 3, 2026). This means: • Available for testing and evaluation • Not yet supported for production workloads • API and behavior may change • Feedback encouraged via

Comparison

| Aspect | Traditional | AI-Driven (MCP) | |---|---|---| | Interface | AAP Web UI | Any AI chat client | | Knowledge required | Template names, parameters | Natural language description | | Steps | 4 (navigate → find → fill → submit) | 2 (open chat → describe) | | Learning curve | Must know AAP UI | Conversational | | Audit trail | AAP job logs | AAP job logs (same) | | RBAC enforcement | Yes | Yes (same AAP RBAC) | | Best for | Power users, routine tasks | New users, ad-hoc requests |

See also: What Is MCP in Red Hat Ansible Automation Platform? Model Context Protocol Explained

Supported AI Clients

The AAP MCP server works with any MCP-compatible client: • ChatGPT (via MCP plugin) • Claude (native MCP support) • Cursor (IDE-integrated) • Any client implementing the MCP standard

FAQ

Does the MCP server bypass AAP security?

No. All requests go through AAP's standard RBAC and authentication. The MCP server authenticates as a specific user/service account with defined permissions.

Can I use this in production with AAP 2.7?

It's a Technology Preview — available for evaluation but not production-supported. GA support is expected in a future AAP release.

What's the difference from the Dev Tools MCP server?

The AAP MCP server is for platform operations (launching jobs, managing inventories). The Dev Tools MCP server is for content development (scaffolding, linting, testing playbooks). They serve different audiences.

Do I still need the AAP web UI?

Yes. The MCP server complements the UI — it doesn't replace it. Complex workflows, configuration, and administration still use the web interface.

Related Articles

• Ansible MCP Server Guide • Ansible Dev Tools MCP Server • Ansible AI-Driven Automation Architecture • Red Hat Ansible Automation Platform 2.7: What's New