GEgetbifrost
MCP

Re-authenticate or edit an MCP session

Mints a fresh authentication flow against the same MCP client and identity as the existing row. Two branches based on row type:

  • OAuth token (any non-orphaned row, typically needs_reauth — but active is also accepted) — opens a fresh upstream OAuth consent flow. Caller is expected to follow authorize_url to the provider; on callback the credential is replaced in place.
  • Header credential (active or needs_update) — opens a fresh per-user-headers submission flow. Caller follows the same URL field to the Bifrost submission form; on submit the credential is replaced in place. kind: "headers" is set on the response.

Refused with 403 if the row is orphaned — a fresh credential wouldn't help; the issue is the identity has lost access to the MCP, which the admin must fix.

post/api/mcp/sessions/{id}/reauth

Request

Path parameters

idstring required

Session row ID (OAuth token or header credential)

Response

Fresh flow opened

authorize_urlstring required

Where the caller must go. For OAuth rows this is the upstream provider's authorize page (via a Bifrost intermediate). For header credential rows it's the Bifrost submission form for the new flow.

submit_urlstring

Set only on header re-auth and identical to authorize_url. Kept for callers that want to be explicit about the underlying surface.

session_idstring required

ID of the freshly-minted flow row

kind'oauth' | 'headers'

Set only on header re-auth

Changes

No recorded changes to this operation across all 1 revision of this API.