Import OAuth tokens
Stores OAuth tokens you obtained yourself (e.g. via the SDK’s runOAuthLogin — interactive loopback, headless, or client-credentials) for this server, scoped to your user, project, and server. Subsequent API calls against the server inject the stored access token automatically, and 401s from the server trigger a server-side refresh — no further caller involvement.
This closes the loop after an OAUTH_REQUIRED error.
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.
ID of the server inside the project.
Body
The MCP server URL the tokens were obtained for.
OAuth protected-resource URL, when it differs from serverUrl.
OAuth client used to obtain the tokens. Optional, but without it server-side refresh cannot run — always include it when you provide a refresh_token.

