AAP Enterprise MCP Server

AAP Enterprise becomes available to MCP clients through the aap enterprise mcp server. A comprehensive Model Context Protocol (MCP) server suite for Red Hat's automation and infrastructure ecosystem, enabling AI assistants to interact with Ansible Automation Platform (AAP), Event-Driven Ansible (EDA), ansible-lint code quality tools, and Red Hat's official documentation with secure.

What AAP Enterprise does

A comprehensive Model Context Protocol (MCP) server suite for Red Hat's automation and infrastructure ecosystem, enabling AI assistants to interact with Ansible Automation Platform (AAP), Event-Driven Ansible (EDA), ansible-lint code quality tools, and Red Hat's official documentation with secure domain validation.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• list_inventories — List all inventories
• get_inventory — Get inventory details by ID
• create_inventory — Create a new inventory
• list_hosts — List hosts in an inventory
• add_host_to_inventory — Add a host to inventory
• run_job — Execute a job template
• job_status — Check job execution status
• job_logs — Retrieve job execution logs
• list_job_templates — List available job templates
• create_job_template — Create a new job template
• create_project — Create a new project
• run_adhoc_command — Execute ad-hoc ansible commands
• list_projects — List all projects
• get_project — Get project details by ID

Installing the aap enterprise mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 7 environment variables: AAP_TOKEN, AAP_URL, EDA_TOKEN, EDA_URL, REDHAT_USERNAME, REDHAT_PASSWORD, MCP_DEBUG. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.11 or higher - UV package manager (recommended) or pip - Access to an Ansible Automation Platform instance - Valid AAP API token

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. AAP Enterprise sits in that group, and the shape of its toolset — list_inventories, get_inventory, create_inventory among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use AAP Enterprise.
• Maintained by sibilleb, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the aap enterprise mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.