Sign in
Environments

Check what this deployment's environment surface supports

Report which environment features this MCPJam deployment accepts. Call it before sending a model override: clients ship independently of the platform, and a field an older deployment does not know is a hard validation error there rather than a silently ignored one. A deployment too old to answer reports false for everything, which is the correct assumption.

get/projects/{projectId}/environments/capabilities

Path parameters

projectIdstring required

ID of the hosted project that contains the server.

Response

The deployment's environment capabilities.

modelOverridesboolean required

modelId is accepted on environment create and update.

modelMatrixboolean required

Environment cells may vary by model on one host (the compare grid).

ephemeralEnvironmentLaunchboolean

startTestSuiteRun / the v1 group route accept ephemeralEnvironment — a project-scoped env may launch without suite membership. Absent or false on older backends.

skillVersionPinsboolean

skillSelection.versionPins and serverSkillSelection.versionPins are accepted, and a pinned revision survives into run snapshots. Absent or false on older backends, which reject the unknown field outright — probe this before offering a version picker.

secretGrantsboolean

secretSelection is accepted on environment create, update and ensure-adhoc, so an environment can carry a credential grant. Absent or false on older backends, which reject the unknown field with a validator error naming nothing — probe this before sending a grant.

Changes

Changed in 4 of the 122 revisions of this API.4