Skip to content
Scalpels home

Scalpels is officially launching on October 31, 2026. Special early adopter pricing is available now.

← All documentation

Documentation

Scalpels

Console

Updated

Console is the authenticated list of Built for Cloud deployments on the selected team. It provides fleet vitals without handing a browser into the deployed application.

Opening /console does not move an application into Scalpels. Each listed deployment remains in the team's own infrastructure.

Who can use it

Every verified team member can open the Console page and see fleet vitals. Console access does not depend on the team's billing state.

Delegated MCP access

Scalpels can relay an MCP request to a deployment on a user's behalf. Each outbound request receives a fresh short-lived assertion containing the user's live identity, effective Console role, target deployment, and a unique request identifier.

The deployment's team and the user's membership are re-read for each request. Team Owners and Admins are delegated as Console Admins; team Members are delegated as Console Members. The assertion is accepted only for the issuer and deployment audience Scalpels provisioned, including for headless apps.

For an agency-backed client team, a user who is also a member of the Agency source team may be delegated with that source membership and the source team named as on_behalf_of. This tells the application both who acted and the team whose authority they used. A user without that source membership uses their membership on the selected client team instead.

Fleet vitals

For each running deployment, the vitals row can show:

  • healthy or degraded status and the Console contract version;
  • application and Built for Cloud package versions;
  • deployment timestamp and age when reported;
  • pending, reserved, and failed queue work, plus the oldest pending age;
  • one optional product-defined headline measurement.

Vitals use a dedicated least-privilege credential for that deployment, not its ownership credential. Unexpected fields or malformed values make the row unavailable instead of being forwarded to the page. A product release that does not publish the vitals endpoint is reported separately from an unreachable or unusable response.