Docs

MCP

Tokens and consent

A connection reaches one project. You choose read, write and publish, and you can revoke it from Connect.

Every connection is limited to one project, and it never exceeds your own role on that project. Read is always included. The other two are optional:

Signing in from the client

When the client can open a browser, AnimSync shows Connect a tool. The heading names the app. You pick the project and the capabilities, then allow or deny. After you answer, the browser returns to that app.

The token issued this way lasts a year. On Connect it is listed with (connected app). Revoke stops it immediately. The confirmation says that anything using it stops working.

A token you create yourself

On the same Connect page, API tokens creates a token for a client that cannot sign in. Give it a name, such as where it will be used, pick the project, and tick write or publish if it needs them.

Copy this token now. It will not be shown again. Only a prefix is stored after that. The token starts with animsync_. It does not expire on its own. Revoke it from the list when you are done with it.

The demo disables Create token and says tokens are not available there.