Session cleanup
When your agent finishes its work, it ends its session with the Model Context Protocol (MCP) server. Ending the session, and optionally expiring the streaming session, releases the underlying streaming instance so the fleet's autoscaling policy can reclaim idle capacity and avoid unnecessary cost. How the agent ends the session, and what happens to the underlying WorkSpaces Applications streaming session, depends on the MCP protocol version. For the supported versions, see Supported MCP protocol versions. On an image builder, ending the MCP session doesn't log out the built-in users. Only stopping the image builder ends its streaming session. For more information, see Image builder sessions.
Stateless MCP protocol
With the stateless MCP protocol (version 2026-07-28), the agent ends the
session by calling the close_session tool. This closes the MCP
session. By default, close_session does not expire the WorkSpaces Applications
streaming session; the streaming instance is preserved for reuse until the
session's disconnect timeout is reached. To also expire the streaming session,
the agent sets expire_streaming_session to true when
it calls close_session. Expiring the streaming session terminates
the streaming instance and triggers the fleet's configured autoscaling policy.
For more information about the tool, see Available tools. For more information about the
disconnect timeout, see Create a Fleet in Amazon WorkSpaces Applications. For more information about
autoscaling, see Fleet Auto Scaling for Amazon WorkSpaces Applications.
Earlier MCP protocol versions
With the earlier MCP protocol versions, you end the session by closing the
MCP client in your agent code. When the MCP client lifecycle ends, the client
sends an HTTP DELETE request to the MCP server. Some agent
frameworks, such as Strands, close the client for you when the session ends.
You control whether ending the session also expires the streaming session by
setting the
x-amzn-agentaccess-expire-streaming-session-on-delete header on
your MCP requests. The following values are available:
-
true– When the MCP client sends the HTTPDELETErequest, the MCP server expires the WorkSpaces Applications streaming session as part of cleanup.-
On a fleet, this terminates the streaming instance and triggers the fleet's configured autoscaling policy. For more information, see Fleet Auto Scaling for Amazon WorkSpaces Applications.
-
On an image builder, this header doesn't end the streaming session. The streaming session and the built-in users that the agent logged in keep running until you stop the image builder. Stopping the image builder ends its streaming session and logs out all users.
-
-
false(default) – The streaming session continues running.-
On a fleet, the session runs until the disconnect timeout is reached. For more information about the disconnect timeout, see Create a Fleet in Amazon WorkSpaces Applications.
-
On an image builder, the session runs until you stop the image builder. For more information, see Image Builder Actions.
-
By default, an mcp-proxy-for-aws MCP client handles the
DELETE request for you when you properly end the client
lifecycle.
Image builder sessions
On an image builder, also keep the following in mind:
-
Ending the MCP session doesn't end the image builder session. The MCP session closes after about 13 minutes of inactivity, or when your agent closes the session. After an idle close, the next tool call reconnects as the last logged-in user.
-
When the image builder session ends, all users are logged out.
-
An image builder is billed while it's running, even after its streaming session ends. Stop the image builder when your agent is done. For more information, see Image Builder Actions.