ちなみに、フォアグラウンドで実行中の npm run dev のターミナルには、やり取りらしきログが表示されていました。
2026-01-25T13:13:47Z Toolset-specific GET request for toolset: job_management
2026-01-25T13:13:47Z Establishing new SSE stream
2026-01-25T13:13:47Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:13:47Z Received MCP request
2026-01-25T13:13:47Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:13:47Z Received MCP request
2026-01-25T13:13:47Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:13:47Z Received MCP request
2026-01-25T13:13:47Z [toolset:job_management] job_templates_launch_retrieve → 200 OK (509ms)
2026-01-25T13:14:12Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:14:12Z Received MCP request
2026-01-25T13:14:13Z [toolset:job_management] job_templates_launch_create → 201 Created (1638ms)
2026-01-25T13:14:28Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:14:28Z Received MCP request
2026-01-25T13:14:29Z [toolset:job_management] jobs_retrieve → 200 OK (983ms)
2026-01-25T13:14:47Z Toolset-specific POST request for toolset: job_management
2026-01-25T13:14:47Z Received MCP request
2026-01-25T13:14:48Z [toolset:job_management] jobs_job_host_summaries_list → 200 OK (937ms)
補足: AAP サーバーアクセス時の証明書検証の有無について
今回は AAP 本体へのアクセス時に証明書検証が成功するような環境でしたが、意図的に検証が失敗するようにしたら mcp.json でサーバーを起動したときに以下のエラーが表示されました（抜粋）。VS Code の [出力] パネルではなく、npm run dev を起動しているターミナル上です。
# This section is for your AAP Gateway host(s)
# -----------------------------------------------------
[automationgateway]
aap26.sakana.local
# This section is for your AAP Controller host(s)
# -----------------------------------------------------
[automationcontroller]
aap26.sakana.local
# This section is for your Ansible MCP Server host(s)
# -----------------------------------------------------
[ansiblemcp]
aap26.sakana.local
# This section is for the AAP database
# -----------------------------------------------------
[database]
aap26.sakana.local
[all:vars]
# Ansible
ansible_connection=local
# MCP Settings
mcp_allow_write_operations=true
# Common variables
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/containerized_installation/appendix-inventory-files-vars#ref-general-inventory-variables
# -----------------------------------------------------
postgresql_admin_username=postgres
postgresql_admin_password=<パスワード>
registry_username=<コンテナレジストリ用Red Hat アカウント>
registry_password=<パスワード>
redis_mode=standalone
# AAP Gateway
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/containerized_installation/appendix-inventory-files-vars#ref-gateway-variables
# -----------------------------------------------------
gateway_admin_password=<パスワード>
gateway_pg_host=aap26.sakana.local
gateway_pg_password=<パスワード>
# AAP Controller
# https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/containerized_installation/appendix-inventory-files-vars#ref-controller-variables
# -----------------------------------------------------
controller_admin_password=<パスワード>
controller_pg_host=aap26.sakana.local
controller_pg_password=<パスワード>
controller_percent_memory_capacity=0.5
2026-01-22 10:55:05.667 [info] 400 status sending message to https://48.218.140.169:8448/mcp/inventory_management, will attempt to fall back to legacy SSE
2026-01-22 10:55:05.737 [info] 接続状態: エラー 404 status connecting to https://48.218.140.169:8448/mcp/inventory_management as SSE: Session not found
※ もし手持ちのライセンスがなければ「trial subscription」のリンクからライアルライセンスを取得して、取得時の Red Hat アカウント情報を「Username and Password」タブで入力すると、下のコンボボックスにトライアルライセンスが表示されるようになるので選択します。
---- name: Facts test Play
hosts: localhost
connection: local
tasks:- name: Facts test
ansible.builtin.debug:msg:"{{ ansible_date_time }}" # トップレベルの変数を参照
Do you plan to make the self-service automation portal available on a RHEL 9 virtual machine or for other non-OCP containerized installations?
Yes, our roadmap includes adding this feature as part of the containerized installer for Ansible Automation Platform with the goal of making it available for all customers regardless of their deployment mechanism.
