Workload sessions are labeled on the MCP Sessions page, and Platform MCP brings existing servers under management
A session opened by a workload no longer looks like a person's. The MCP Sessions page marks those rows as workloads, names the issuer they came from, shows the agent they act through, and lists every admission currently letting them in. The revoke dialog spells out which controls actually stop a workload, ordered from narrowest to widest, so nobody mistakes ending one session for cutting off access. Platform MCP setup gains an optional step for bringing the remote MCP servers already configured in Claude Code under management, and remote MCP URLs report structured probe outcomes instead of a single pass or fail.Features
- Workload sessions named and explained #6503 -
userSessions.listreturns aworkloadobject forworkload:subjects carrying the workload issuer's name and URL, the external subject, the assigned agent and its state, and every project or organization tier admission currently letting the workload in. The dashboard marks these rows as workloads rather than people. The revoke dialog lists the controls that can stop a workload, narrowest to widest, and shows which ones stop it from reconnecting: revoking a workload session ends only that session, and the workload can exchange a new token and reconnect. (Author: @aa-wong) - Bring existing Claude Code MCP servers under management #6518 - Platform MCP setup gains an optional second step for adopting remote MCP servers already configured in Claude Code. The workflow verifies the agent's connection, asks for informed discovery consent or a sanitized manual inventory, and prefers catalogue entries matched by endpoint or confirmed provider and name before falling back to custom URLs. It confirms the destination and the selected servers, then reports each registration separately. Authentication stays on the platform, with no local credentials migrated. (Author: @alx-xo)
- Structured probe outcomes for remote MCP URLs #6357 - A new
probeURLendpoint distinguishes availability, authentication, invalid-response, and unreachable outcomes, so a URL that needs credentials reads differently from one that cannot be reached. The deprecatedverifyURLendpoint stays for compatibility. (Author: @qstearns)
