AAP Enterprise MCP Server provides a four-server architecture to integrate Ansible Automation Platform (AAP), Event-Driven Ansible (EDA), Ansible Lint, and Red Hat Documentation. The ansible server exposes inventory, project, and job management capabilities that let you list inventories, create projects, run job templates, and retrieve logs. The eda server handles activation and rulebook management for event-driven automation and supports querying decision environments and streaming events. The ansible-lint server performs real-time playbook validation, file analysis, and rule management to enforce best practices. The redhat-docs server offers streamlined access to official Red Hat documentation with domain validation and a PDF-first fetch flow to handle dynamic content. You can coordinate these servers from your MCP client by configuring each server to run with UV, pointing to the server directory, and supplying the appropriate API tokens and endpoints. Together, these tools enable end-to-end automation, governance, and documentation access within a single MCP ecosystem.

Prerequisites:

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

Setup steps:

1. Clone the repository: git clone https://github.com/sibilleb/AAP-Enterprise-MCP-Server.git cd AAP-Enterprise-MCP-Server

2. Install dependencies (choose UV or pip):

   Using UV (recommended)

   uv sync

   Or using pip

   pip install -e .

3. Configure environment variables (example):

   Required for AAP/EDA servers

   export AAP_TOKEN="your-aap-api-token" export AAP_URL="https://your-aap-server.com/api/controller/v2" export EDA_TOKEN="your-eda-api-token" # Can be same as AAP_TOKEN export EDA_URL="https://your-aap-server.com/api/eda/v1"

   Optional for Red Hat Customer Portal access

   export REDHAT_USERNAME="your-redhat-username" export REDHAT_PASSWORD="your-redhat-password"

4. Run the servers via MCP client configuration (see mcp_config example) or run locally with UV as described in the repository docs.

Tips and known considerations:

• Ensure the AAP/EDA endpoints are reachable from the host running the MCP servers and that tokens have appropriate scopes.
• When using redhat-docs, provide REDHAT_USERNAME and REDHAT_PASSWORD if you need access to restricted content; otherwise, public content may be used.
• The SSL/TLS settings in this project are designed to skip certificate verification in lab environments; for production, configure proper certificates on your AAP instance and disable insecure options.
• If you modify the path /path/to/AAP-Enterprise-MCP-Server, make sure all mcpServers entries reflect the correct directory.
• The four-server setup isolates concerns, making it easier to scale individual components according to load and feature usage.