Tokens

A personal access token is how an MCP client proves it is acting for you. Mint one in Settings → Access tokens.

Tokens start with kan_pat_.

Shown once

The token is displayed exactly once, when you create it. We store only a hash, so we cannot show it to you again and cannot recover it if you lose it. Copy it straight into your client’s configuration.

Lost one? Revoke it and mint another. That is the whole recovery procedure.

No scopes, no expiry

Say this plainly rather than letting you infer a permission model that doesn’t exist:

• There are no scopes. A token can do everything the tools can do — create sites, replace their contents, change visibility, list what you have. There is no read-only token and no per-site token.
• There is no expiry. A token works until you revoke it.

So a token is worth protecting like a password. Keep it out of anything you share — repositories, screenshots, pasted config, chat logs with people who aren’t you.

One per client

Mint a separate token for each client you connect. They are free, and it means revoking one doesn’t disconnect the others.

Revoking

Revoke in the same place you minted. It takes effect immediately: the next request from that token gets a 401, and the client will report that it can no longer reach the server.

Revoking a token does nothing to the sites it published. They stay live and stay yours.