Open Automation Platform MCP Server
Allows interaction with Red Hat Ansible Automation Platform (AAP), providing tools for listing job templates, inventories, collections, EDA activations, reading audit events, performing policy dry runs, and launching job templates with RBAC and policy enforcement.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Open Automation Platform MCP Server list job templates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Open Automation Platform MCP Server
A Model Context Protocol (MCP) server that exposes open automation platform capabilities to AI agents and assistants. It is the open implementation of the AAP 2.7 MCP server.
Every tool call is governed the same way a human action is:
Gateway auth — platform data is read/written only through the gateway origin, using the caller's token.
RBAC scope — each tool requires a scope; a caller lacking it gets an explicit error, never a silent allow.
Policy — mutating tools (e.g.
launch_job_template) build aPolicyContextand call the policy service first; a denial blocks the action before it reaches the gateway. Fail-closed if the policy service is unreachable.
So an agent can never exceed the caller's RBAC or bypass policy.
Tools
Tool | Scope | Action |
|
| List controller job templates. |
|
| List inventories. |
|
| List hub collections. |
|
| List EDA activations. |
|
| Read normalized audit events. |
|
| Evaluate a PolicyContext with no side effect. |
|
| Launch a job template (policy-checked). |
platform:admin satisfies any scope.
Related MCP server: ansible-aap
Protocol
Conformant JSON-RPC 2.0 MCP core — initialize, tools/list, tools/call,
ping — implemented dependency-free so the server is self-contained. It can be
swapped for the official MCP SDK without changing the tool or client layers.
Transports: newline-delimited JSON-RPC over stdio (the standard local MCP
transport) and an HTTP JSON-RPC endpoint (POST /, GET /healthz) for the
platform.
Run
# stdio (per-agent), identity/scopes from env
GATEWAY_URL=http://awx-gateway:8080 POLICY_URL=http://policy:8181 \
MCP_AUTH_USER=agent MCP_AUTH_TEAMS=sre MCP_AUTH_SCOPES=controller:read,controller:launch,policy:read \
MCP_AUTH_TOKEN=... node src/index.mjs
# http (platform service)
MCP_TRANSPORT=http MCP_ADDR=0.0.0.0:8765 node src/index.mjsValidate
scripts/local-validation # node --check every module + node --testZero runtime dependencies (Node 20+ built-in fetch, http, readline,
node:test). Container base and all images are public/community; no
authenticated Red Hat registry.
Available Tools
7 toolslaunch_job_templateB
Launch a controller job template. The action is policy-checked before it runs; a policy denial blocks the launch.
Inputs: template_id (required), forks, inventory, extra_vars, +2 more.
list_collectionsB
List automation hub collections.
Inputs: no named parameters.
list_eda_activationsA
List Event-Driven Ansible rulebook activations.
Inputs: no named parameters.
list_inventoriesB
List automation controller inventories.
Inputs: no named parameters.
list_job_templatesA
List automation controller job templates the caller can see.
Inputs: no named parameters.
policy_dry_runC
Evaluate a PolicyContext without performing any action; returns allow/deny with reasons.
Inputs: policy_context (required).
read_audit_eventsB
Read recent normalized platform audit events.
Inputs: limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct resource or action: listing various entities (job templates, inventories, collections, EDA activations), reading audit events, performing a policy dry-run, and launching a job template. No overlapping purposes.
Mix of prefixes: list_ for four tools, read_ for one, launch_ for one, and policy_dry_run as a phrase. Not fully consistent but still readable.
Seven tools is a well-scoped set for an automation platform, covering core viewing and launch operations without being overwhelming.
Missing create/update/delete operations for resources like job templates and inventories. The server is limited to listing and launching, with a dry-run policy check, but lacks basic CRUD, which may cause agent failures when needing to manage resources.
Maintenance
Related MCP Connectors
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Related MCP Servers
- FlicenseCqualityDmaintenanceEnables comprehensive management of Ansible Automation Platform Controller and Gateway through 17 specialized tools covering job execution, inventory management, workflows, credentials, user administration, and system monitoring.18-
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to discover and launch Ansible job templates on Ansible Automation Platform, monitor job status, and retrieve outputs.4-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and call existing OpenAPI services through governed tools, enforcing policy, approval for destructive operations, and credential handling before requests execute.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to inspect, query, and diagnose an Octopus instance and perform release, deployment, runbook, and feature-toggle operations via curated tools and a REST backstop.547 npmMIT