Agents that know Jira from ServiceNow

This sprint

The web UI has spoken ITSM for a while: Jira or ServiceNow, same ticket workflow. IDE agents still had not caught up.

Cursor and other agents still saw post_jira_transition. AAP job-template tools still offered transition_jira. There was no way for an agent to learn — without secrets — whether the signed-in operator was on Jira or ServiceNow, what default project applied, or which AAP project id was configured.

Sprint 112 ships ITSM MCP consistency + effective settings: agents call ITSM tool names, the leftover Jira MCP names are gone, and a non-secret effective-config tool tells the agent which world it is in.

What moved

Call get_effective_settings to learn:

• itsm.provider — jira or servicenow
• effective ITSM / AAP URLs
• default project / source id
• AAP project_id
• selected completeness flags

Use this before get_itsm_default_tasks when the agent needs to know which ITSM the operator is on.

The PAT you mint in Configuration → MCP Connect already acts as that user. Effective settings now expose that user’s defaults without leaking tokens into the tool result.

Still open

On purpose, this slice does not:

• Rename the product away from ITSM
• Polish Settings / Task List copy in the web UI
• Delete leftover /jira/* HTTP aliases (MCP and new paths call /itsm/...)
• Change get_itsm_default_tasks or the ITSM provider id

Secrets stay out of the effective payload entirely.

For customers

• IDE agents: prompts and Skills can name ITSM tools without teaching a Jira-only world. Anything still calling post_jira_transition or transition_jira needs an update.
• ServiceNow labs: agents can discover provider: servicenow without opening System Settings or guessing from task keys.
• Operators: PATs from MCP Connect already act as the user; effective settings finally expose that user’s defaults without tokens in the result.

The appliance has been ITSM-neutral on the ticket layer. This sprint makes the MCP contract catch up — and gives agents the config context they need to act on it.

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: confirm provider via MCP, refresh backlog, and optionally transition with the new tool name.

1. Effective settings

Use get_effective_settings and tell me whether this user is on Jira or ServiceNow,
and what default_project_key and aap.project_id are.

Confirm the response has itsm.provider and no token fields.

2. Refresh backlog

Use get_itsm_default_tasks to refresh the default ITSM backlog.

3. Transition (optional)

Use post_itsm_transition for <TASK_KEY>.

4. AAP job-template flag (optional)

Create or resolve a job template with post_aap_job_template and transition_itsm: false (the default). Do not send transition_jira.