Skip to main content
Every interface signs in to the same Rippit account. Your role in the workspace decides what you can do: operations that change workspace setup, such as connecting a data source, need a workspace admin, and return 403 otherwise.

​
AI assistants (MCP)

Add Rippit as a connector in your assistant and sign in through the browser when it asks. The assistant never sees a password or token. See supported clients for setup steps per assistant.

​
API tokens

Every operation in this reference works through MCP, where your sign-in handles auth. That sign-in is short-lived, so anything that runs on its own, like a scheduled upload to the Bulk API, needs an API token, sent as a bearer token:
Create one with rippit token create, or in Rippit chat: ask to “connect via API” and click Create API token. The full token is shown once, so copy it right away. Tokens expire after a year by default; pick a shorter or no expiry when you create one, and revoke one with rippit token revoke <id>. Treat a token like a password: keep it out of source code and out of chats with your assistant.

​
Rippit CLI

It opens a browser to confirm, then keeps you signed in. Without an account, choose Sign up on that page. See Rippit CLI.