Ansible Automation Platform Partner ConnectorConnect Ansible Automation Platform Without Constraints
IntelliPaaS seamlessly connects Red Hat Ansible Automation Platform with your core business systems, enabling no-code integration for remediation, provisioning and compliance automation across cloud, on-prem and hybrid environments.
Red Hat's MCP server for Ansible Automation Platform runs inside your own AAP deployment rather than on vendor infrastructure — installed by the containerised installer on RHEL or through the AAP Operator on OpenShift — so residency follows wherever you already run AAP. It reached general availability in mid-2026 after a technology preview in 2.6.4. Authentication is OAuth 2.1 or a personal access token, and permissions work in two layers: what the server is configured to expose at all, combined with the user's own AAP role-based access, so an agent cannot get past controls you already have. Toolsets cover job management, inventory, system monitoring, user management, security and compliance, and platform configuration. A discover endpoint keeps agents from having to load the entire tool list. One naming trap worth avoiding — AAP's separate MCP server integration feature is the reverse direction, AAP acting as a client.
Ansible Automation Platform integration capabilities
- Launch jobs and monitor their status through job management tools.
- Read and manage inventory hosts and group membership.
- Read logs and troubleshoot failures through system monitoring tools.
- Read users, access and organisation structure.
- Work with credentials and integrity checks under security and compliance tools.
- Use the discover endpoint to load only the tools a workflow needs.
These capabilities let automation be triggered and tracked by the systems that notice a problem, without anyone opening the AAP console. IntelliPaaS handles field mapping, approval routing and data type transformation automatically.
Common integration scenarios
- Launch a remediation job automatically from a PagerDuty, Datadog or Splunk alert.
- Run provisioning playbooks when a ServiceNow or Jira request is approved.
- Sync inventory and group membership with the CMDB or cloud asset inventory.
- Post job outcomes and failure summaries into Slack or Microsoft Teams.
- Run scheduled compliance checks and report results into a governance register.
These scenarios address the most common friction in operations automation — runbooks that need a human to press the button, inventory that drifts from the CMDB — by automating the flows between AAP and the platforms around it.
Deployment & security
Flexible deployment is essential for organisations operating in regulated industries or jurisdictions with strict data residency requirements. IntelliPaaS supports private cloud and on-premise deployments with full regional data sovereignty, and because the AAP MCP server runs inside your own deployment there is no vendor-hosted endpoint at all. All deployment modes receive the same feature set, connector library and support tier, with no capability trade-offs based on deployment choice.
Why IntelliPaaS
- No-code to pro-code flexibility for all integration needs.
- End-to-end security with OAuth 2.1 and dual-layer server and AAP RBAC permissions.
- Runs inside your own AAP deployment, so nothing crosses a vendor boundary.
- Enterprise-grade observability with monitoring, alerting and audit logging.
Frequently connected apps
Jenkins
GitHub
GitLab
Azure DevOps
ServiceNow
Datadog
Splunk
PagerDuty
ActiveDirectory
Microsoft AzureFrequently asked questions
What authentication does the connector use?
OAuth 2.1 or a personal access token. Permissions are dual-layer — what the server is configured to expose, combined with the user's own AAP role-based access — so an agent cannot bypass existing controls.
Where does the server run?
Inside your own AAP deployment. It is installed by the containerised installer on RHEL, or through the AAP Operator on OpenShift, and served over HTTPS from your own host. There is no Red Hat-hosted endpoint.
Is this the same as AAP's MCP server integration feature?
No, and it is an easy confusion. That feature is the reverse direction — AAP execution environments acting as an MCP client to third-party servers. This connector is about agents driving AAP.
Can I deploy on-premise or in a private cloud?
Yes, and this connector is a particularly good fit for it. Cloud (SaaS), private cloud in your own VPC, and fully on-premise or air-gapped deployments are all supported, with full feature parity across every mode.
Is my data secure?
Data is encrypted in transit and at rest, and IntelliPaaS is GDPR-ready. Red Hat documents distinct protection levels and filtering for credentials held outside AAP's standard credential system, and because the server is yours, nothing leaves your infrastructure boundary.