1
Find the provider
2
Connect it
For an OAuth provider, this opens your browser:On a machine without a browser, print the URL instead:For an API-key provider, pass the key:By default the credential lands in the vault for that workspace. To place it elsewhere — an org vault, so several teams can share it — name the vault:
Choosing where a credential lives is the main decision here. A workspace vault keeps it to one team. An org vault lets you share it — and then control who gets it with credential scope.
3
Confirm it works
4
Confirm agents will get the right one
Sharing a credential across teams
Put it in the org vault, then scope it:GitHub needs a token for private repos
Signing in with GitHub grants public access only. To read private repositories — for skill sources or MCP repositories — connect a personal access token with therepo scope. See Connect GitHub for private repos.
Removing a connection
What agents see
A skill declares the services it requires. At run time, JoyStream resolves a credential for each and hands it to the MCP server in the environment variable that server expects. If a required credential is missing, the run stops and names the provider to connect — it does not guess. See Credentials and vaults for how the environment variable is chosen.See also
jstm connection— full reference.- Credential problems