See the ticket, see AAP

This sprint

Sprint 112 taught IDE agents which ITSM they were on (get_effective_settings) and finished toward-ITSM naming. They could still refresh a default backlog of keys and summaries, but then they might have to guess about deeper request details.

They could not read a ticket’s description or comments. They also could not browse a non-default ITSM source. They could not list Controller projects or the job templates already in the effective AAP project. Controller deep links were thin or missing. Generate → job-template create worked, but the agent operated half-blind.

Sprint 113 ships MCP see the ticket + see AAP: read-only discovery so agents can inspect context before they act.

What moved

Same capability ids on HTTP /mcp/ and stdio.

ITSM context

Use get_effective_settings, then get_itsm_task_details for <TASK_KEY>.
If needed, get_itsm_sources / get_itsm_source_tasks / get_itsm_source_statuses
to work beyond the default project.

Details include an ITSM deep_link when the provider base URL is known.

AAP discovery

Use get_aap_projects and get_aap_job_templates (optional name filter).
Confirm the effective project and whether a job template already exists before
post_aap_job_template.

Job-template rows may include template_ui_url; projects may include project_ui_url.

Still open

On purpose, this slice does not add:

• Job status / stdout / wait after gated launch
• ITSM comment write-back
• Crane mutations over MCP
• Job launch from the web UI

Secrets stay out of discovery payloads. post_aap_launch remains policy + confirm: true.

For customers

• IDE agents can read the ticket before generating a playbook, and check existing job templates before create/apply.
• AAP operators can verify the project id and jump to Controller UI without leaving the IDE chat.
• Multi-project ITSM labs can browse sources beyond the user default without opening the web UI.

Situational awareness was the missing half of ticket → playbook → job template. Observe-after-launch comes next.

PAT and transport: MCP quickstart (Configuration → MCP Connect). After you take the appliance update, fully restart the IDE MCP process so the tool list refreshes.

Try it (about five minutes)

Goal: inspect a ticket and AAP inventory via MCP, then optionally create/apply a job template with eyes open.

1. Effective settings + ticket details

Use get_effective_settings. Then get_itsm_task_details for <TASK_KEY>
and summarize the description. Include the deep_link if present.

2. Optional non-default source

Use get_itsm_sources, pick a source_id, then get_itsm_source_tasks
and get_itsm_source_statuses for that source.

3. AAP browse

Use get_aap_projects and get_aap_job_templates.
Tell me the effective project_id and whether a job template named like <TASK_KEY> already exists.
Include any template_ui_url / project_ui_url.

4. Optional job-template apply

Use get_check_playbook then post_aap_job_template for <TASK_KEY>
(with config_yaml if available). Do not launch unless I explicitly confirm.

Sprint 112 made agents speak ITSM. Sprint 113 lets them look before they automate.