Render an MCP App widget headlessly
Call an MCP App tool and mount its ui:// widget in real headless Chromium running the production host bridge, then report whether it rendered, what it logged, what it was blocked from fetching, and the widget as an accessibility tree with addressable elements.
Executes the tool, so it has whatever side effects that tool has: the render is what happens afterwards.
Stateless: connect, call, render, read, dispose, all inside one request. Interactive widget sessions use the local Inspector’s /api/v1/projects/{projectId}/servers/{serverId}/widget-sessions endpoints. They hold a live browser in process and return 404 on hosted deployments without session affinity.
Each render launches a browser, so the endpoint carries a per-replica concurrency cap and answers 429 when it is full.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
Body
Response
The render verdict and its evidence.

