Skip to main content
Glama
Open Automation Platform MCP Server

Open Automation Platform MCP Server

by joenukem

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:

  1. Gateway auth — platform data is read/written only through the gateway origin, using the caller's token.

  2. RBAC scope — each tool requires a scope; a caller lacking it gets an explicit error, never a silent allow.

  3. Policy — mutating tools (e.g. launch_job_template) build a PolicyContext and 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_job_templates

controller:read

List controller job templates.

list_inventories

controller:read

List inventories.

list_collections

hub:read

List hub collections.

list_eda_activations

eda:read

List EDA activations.

read_audit_events

audit:read

Read normalized audit events.

policy_dry_run

policy:read

Evaluate a PolicyContext with no side effect.

launch_job_template

controller:launch

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.mjs

Validate

scripts/local-validation   # node --check every module + node --test

Zero 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 tools
launch_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

    B3.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    Seven tools is a well-scoped set for an automation platform, covering core viewing and launch operations without being overwhelming.

    Completeness2/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and call existing OpenAPI services through governed tools, enforcing policy, approval for destructive operations, and credential handling before requests execute.
      1
      Apache 2.0