Tokens
How Web Anatomy MCP tokens work — generate once, regenerate if lost, revoke when done.
Your MCP token is created and managed in the MCP dashboard, after your private beta access is approved.
The token is shown once
When you generate a token, the full value appears one time, in a copyable field at the top of the "Set up your agent" card. Copy it then. Web Anatomy stores only a one-way hash, so the full token can never be shown again.
Have your IDE config or terminal ready before you generate, so you can paste the token while it is on screen. After you leave or refresh the page, the field is replaced by a masked preview (wa_beta_...XXXX) and the full value is gone.
Lost your token? Regenerate it
If you navigated away before copying, or you no longer have the token, you do not need to recover the old one. On the dashboard, click Regenerate token. This issues a fresh token, shown once.
Regenerating invalidates the previous token. Any IDE or agent already configured with the old token stops connecting until you update it with the new value.
Revoke a token
Click Revoke token in the dashboard to disable a token without issuing a new one. Use this if a token may have leaked (committed to a repo, pasted into chat logs, or printed in shell history). The revoked token stops authenticating immediately. Generate a new one when you are ready to reconnect.
Where the token goes
Once you have a fresh token, paste it into your IDE's config using the setup guide for your client. Keep it in user-level (global) config so it is never committed. See Authentication for storage guidance.