Standalone MCP server configuration reference

Environment variables, network ports, container images, and toolsets for the standalone MCP server deployment.

Environment variables

Configure the standalone MCP server using these environment variables when starting the container.

Variable Required Default Description
BASE_URL Yes https://localhost The AAP instance URL
IGNORE_CERTIFICATE_ERRORS No false Set to true for self-signed certificates (development only)
MCP_PORT No 3000 Port the MCP server listens on
ALLOW_WRITE_OPERATIONS No false Enable POST, PUT, PATCH, and DELETE operations
SESSION_TIMEOUT No 1200 Session timeout in seconds
ENABLE_METRICS No false Enable Prometheus metrics at /metrics

Network ports

The standalone MCP server uses these network ports depending on the deployment configuration.

Port Description
3000 Direct HTTP access to the MCP server. No TLS. Use -p 3000:3000 when starting the container.
8448 HTTPS via nginx. Use -p 8448:8448 when TLS is enabled.
8086 HTTP redirect to HTTPS on port 8448 (TLS mode only).

Container images

The MCP server is version-specific. Use the container image that matches your AAP version.

AAP version Container image
AAP 2.6 registry.redhat.io/ansible-automation-platform-tech-preview/mcp-server-rhel9:latest
AAP 2.7 registry.redhat.io/ansible-automation-platform-27/mcp-server-rhel9:latest
Important
API changes between AAP 2.6 and AAP 2.7 mean that not all tools will work correctly if the MCP server version does not match the AAP version. Always use matching versions.

MCP toolsets

The MCP server organizes AAP functionality into toolsets. Each toolset provides access to a specific area of AAP functionality through the Model Context Protocol.

Toolset Description
job_management Job templates, jobs, workflow jobs, projects
inventory_management Inventories, hosts, groups, host variables
system_monitoring Instance groups, activity stream, mesh visualizer, status
user_management Users, teams, organizations, roles, authenticators
security_compliance Credentials, credential types, audit logs
platform_configuration Settings, execution environments, notification templates

MCP client URL pattern

MCP clients connect to the standalone MCP server using this URL pattern:

http://localhost:3000/mcp/<toolset>

When TLS is enabled, use:

https://localhost:8448/mcp/<toolset>

Replace <toolset> with one of the toolset names from the table above.