LabscoMCP early access ↗
jd1306MCP SERVER

Aap MCP

Query and launch Ansible Automation Platform jobs, templates, workflows, inventory and nodes from an MCP client.

by jd1306 ↗Cloud Resources & Infrastructure as CodeCommunity

LABSCO SUMMARY

Launch the job and read its output in the same place.

run_job and get_job_output together are what make this more than a dashboard reader — the loop of launching a template and reading why it failed stays inside the conversation. Credential handling is the other considered part: the Keychain path means the token does not have to sit in a config file.

What it is

A Node MCP server for Ansible Automation Platform (AAP) 2.4. It wraps the AAP API so an assistant can look at what is running, launch a job template, and read the output back without opening the AAP console.

What you get

  • System — get_system_info, get_platform_metrics for platform capacity and job statistics
  • Jobs — list_jobs with filtering, get_job, run_job to launch a template, get_job_output for the execution log
  • Templates — list_job_templates, list_workflow_templates
  • Workflows — list_workflow_jobs, get_workflow_job
  • Inventory — list_hosts, list_groups
  • Projects — list_projects, get_project
  • Infrastructure — list_nodes for control and execution nodes, get_node_details

Requirements

Node.js 18.0.0 or higher, and access to an AAP instance. AAP_BASE_URL is required, plus either AAP_TOKEN or the pair AAP_USERNAME and AAP_PASSWORD. Credentials are resolved in priority order — environment variables first, then the macOS Keychain, then a .env file — and npm run setup-keychain walks the whole choice interactively, including hidden password entry. AAP_CONFIG_DIR and AAP_DATA_DIR override the default directories.

Setup effort

Build from source — git clone https://github.com/jd1306/aap-mcp.git

See installation options