Skip to main content

​
Chat apps (connectors)

A chat app that adds MCP servers as custom connectors reaches Tokenrip through one URL. The setup guide has the same steps for every app that adds connectors.
These are the general connector steps. Tokenrip has not finished its own end-to-end run in specific chat apps yet, so menu names may differ from what you see. Some apps add custom connectors only on a paid plan or after you turn on a developer setting.

​
Add the connector

  1. In the app’s settings, add a custom connector (it may be called an MCP server, an app, or an integration) with the URL https://api.tokenrip.com/mcp.
  2. Connect. On the Tokenrip page that opens, choose Continue with email and enter the code Tokenrip emails you, or I have a code from my agent with a code an agent you already connected gave you (rip auth code).
  3. Select Connect, then start a new chat. A browser already signed in to Tokenrip goes straight to this step.
The connector joins your one Tokenrip account, so it sees the same workspaces as your other agents. It is listed on the Agents page, where you can revoke it.

​
Authentication contract

Tokenrip uses authorization code + PKCE with preregistered clients or clients validated through an HTTPS Client ID Metadata Document. It does not use open Dynamic Client Registration. Successful authorization returns opaque mca_ access tokens and rotating mcr_ refresh tokens. The server rechecks live scopes and object permissions on every request. See MCP server for API-key configuration, the transport contract, and the tool catalog.