Before you start
Sign in to the intended Account identity and use an agent application with private MCP connection settings. The token does not create missing service permissions.
What to do
- Open Account and select Agent access. Review the active token or use Create token when none is active.
- Choose a recognisable token name and expiry. The offered choices include 30, 90 or 365 days, a future custom date, or Until revoked. Save changes separately when editing an existing token's name or expiry.
- After creation, copy the token and the configuration for your chosen agent application into that application's private connection settings. The secret is shown only at creation; an existing configuration may contain YOUR_YASA_TOKEN for you to replace with the secret you saved.
- Ask the connected agent to list the Yasa resources it can access and check the intended resources. Use I saved it — hide token when you have stored the configuration safely.
- If the secret is lost or needs replacement, review the Replace token confirmation, then update every agent that used the old token. Use Revoke token only when you intend to stop every agent using it.
- If Previous hosting agent connections is shown, keep those connections until the replacement token has actually connected. Retire legacy MCP connections becomes available after the server verifies the replacement connection; retiring them stops their old configurations while SFTP remains separate.
What happens next
The configured agent can discover the resources permitted to your identity. Token status, expiry, last use and history can be reviewed in Account; these do not grant host administration or access to other people's resources.
If something goes wrong
Do not paste a token into a chat, screenshot or repository. Check expiry, revocation, the selected identity and the agent's private configuration when access fails. After an uncertain replacement or revocation, reload the token status before repeating it. A missing resource requires its owner's permission, not another token. Contact Yasa with the affected service and error, excluding the secret.
