V8Chat shows a newly created personal access key in full only once and stores only its SHA-256 hash on the server.
Every personal key is bound to the user and the selected V8Chat workspace. A connected application cannot simply point the key at another workspace by supplying a different organization.
When you disable MCP in your account, existing personal keys are blocked immediately. Rotating a key revokes previous active keys for the same user and workspace.
Do not place the key in public repositories, tickets, screenshots or shared notes. If you think it has been exposed, revoke or rotate it immediately.
Developers can find the technical interface reference at /en/interfaces/mcp, including protocol versions, tool schemas, example requests and error codes.