Claude and ChatGPT connect by opening a Clipses login page. Some editors and other MCP clients cannot do that, so they use an API token instead. A token grants the same access as a login: every project and transcript in your account. Treat it like a password.
- Log in to Clipses and open Settings from the sidebar.
- Scroll to the API Tokens section.
- Under New token name, type a name that tells you which tool it is for, for example the tool's name.
- Click Create token.
- Click the copy button next to the token, or select and copy it. It is shown once only.
- In your tool's MCP settings, add a server with the URL https://api.clipses.ai/mcp and set the Authorization header to Bearer followed by a space and your token.
- Back in Clipses, click Done, I copied it.
If you lose the token
Clipses only keeps the last four characters, so a lost token cannot be shown again. Click the trash icon next to it, then Revoke token, and create a new one. The token list shows when each token was last used, which helps you spot one that is no longer needed.
What a token can and cannot do
A token gives the tool the same access as a connected assistant: it can read, search, tag, import from Google Drive, and render reels, and it cannot delete anything or touch billing. Searches through a token are free, the same as through a connected assistant. Tokens only work for connecting AI assistants and tools over MCP. They are not credentials for a general Clipses API, and there is no separate developer API. For client-by-client setup, see the full connection guide.
Still stuck? Email hello@clipses.ai.