Update a scenario
Change a scenario’s identity or its exposure — but not both in one call. Send mode on its own. Identity and exposure are separate operations upstream, and applying them in sequence could leave the scenario live in a mode you did not ask for.
Narrowing mode bumps accessVersion upstream and invalidates sessions minted under the old one.
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
ID of the hosted project that contains the server.
Scenario ID, as returned by publishing an environment or by the project's scenario reads.
Body
At least one field. Send mode on its own: identity and exposure are separate operations upstream, and applying them in sequence could leave the scenario live in a mode you did not ask for.
2002000Who may open the share link:
project_members— signed-in members of the project onlyinvited_only— named members, invited individuallyanyone_with_link— anyone holding the URL, signed in or not
project_members, invited_only, anyone_with_link Response
The updated scenario.
Scenario metadata after an update. Deliberately WITHOUT accessVersion: a mode change bumps it upstream, but the envelope this route re-reads does not carry the new value — reporting a stale one would document a revocation signal the response cannot deliver. The publish response carries the real one.

