Can’t sign in
I’m getting an error or can’t sign in
- Try signing in to Rippit again from your client’s connector or MCP settings.
- If that doesn’t help, remove the Rippit entry and add it again so it runs a fresh sign-in.
- If you still can’t get in, your organization may not have access enabled yet.
Admin help needed for step 3. Contact your Rippit point of contact to confirm access for your organization.
The sign-in screen didn’t open in my browser
If your assistant is running on a remote machine (over SSH or a cloud workspace), it can’t open a browser locally. It should print a sign-in link in the terminal or chat. Copy that into a browser on your own computer to finish signing in.The consent screen says the client is “unverified”
Expected, not an error. Clients that register themselves with Rippit (ChatGPT, Codex, Cursor, Copilot, and anything connecting as any MCP client) are labeled unverified with self-reported details. Approve and continue. See Security for why.Sign-in worked but I’m told registration expired
A client’s self-registration is held for one hour before it expires. If you left the browser window open and came back much later, start the sign-in again rather than retrying the stale window.The connector goes red right after sign-in
Claude
No answers, or the wrong ones
Rippit isn’t responding to my questions
The cause differs by client:- Most clients: mention Rippit explicitly in your prompt, for example “Use Rippit to list my workbooks.” Assistants need that nudge to pick the right tool.
- ChatGPT: Rippit must be selected for the conversation you’re in, not just connected. Use the + (tools) menu, or select it beneath the composer in a new chat. No amount of prompting works until it’s selected.
- Copilot Studio: the agent decides whether to call Rippit based on the server description you entered. A vague description means it gets skipped. If it calls Rippit but then asks you which column to aggregate or filter, it needs agent instructions.
Rippit isn’t listed in my settings at all
ChatGPT · Claude
Admin help needed. Ask your admin to confirm Rippit is installed for your workspace and that your account is in scope.
Failures
Tool calls keep failing
Sign in to Rippit again from your client’s settings. If failures persist, the access token may not be refreshing or the server may be unreachable.Admin help needed if failures persist. Have your admin run
curl https://mcp.rippit.com/.well-known/oauth-protected-resource to check the server. A 200 with JSON means the server is up and the problem is on the client side. A 404 or timeout means the server itself is unreachable.”OAuth token has been invalidated”
Claude
Sign-in fails and my client asked for a Client ID
Most clients get their credentials from Rippit automatically, so no setup form should require one. Gemini Enterprise is the exception: it requires a client ID, and the value to use is on the Gemini Enterprise page. If any other client insists on a client ID before it will connect, contact your Rippit point of contact, and include the callback URL the client displayed. Do not generate a client ID yourself in an API testing tool such as Postman. That client is registered against the tool’s own callback URL, so sign-in then fails withinvalid_redirect_uri.
Missing charts or visuals
Charts or images in the answer aren’t loading
Your browser or company network might be blocking one of Rippit’s hosts.Admin help needed. Ask your IT admin to check that
cdn.rippit.com is allowed through any browser extensions or corporate proxies. See Security for the full list of hosts.I don’t see charts at all, just text
Interactive Ask Rippit cards render only in clients that support MCP UI cards, which today means Claude. Other clients receive the same answers as text and data. See Supported clients.Copilot Studio can’t reach Rippit
Microsoft Copilot
Rippit Agentic Chat
Issues with MCP servers you have connected to Rippit’s in-app agent. See Connect a server for setup.A connection says “Reconnect needed”
Its credential can no longer be refreshed, usually because access was revoked on the provider’s side, a password or token changed, or a long-lived grant expired. Open Connections → MCP Servers and click Reconnect. Your tool selection is preserved. Other connections keep working in the meantime. Only the unhealthy server’s tools are withheld.It connected, but no tools loaded
Rippit saved the connection but the server did not return a tool list. Try Manage tools to retry. If it keeps failing, the usual cause is a server that holds its initial connection open as a long-lived stream, which fails the tool-list step even though the agent could call the server fine. Contact your Rippit point of contact if a server you expect to work never lists tools.The agent won’t use a tool I expect it to have
Check three things, in order:- Is the tool enabled? Open Manage tools on the connection. Connections start read-only, so anything that writes is off until someone turns it on.
- Was it added by the provider recently? Rippit refreshes a server’s tool list on connect, reconnect, reset to read-only, and when you open the tool picker, not on every run. Use Reset to read-only, then re-select, to pick up new tools.
- Is the connection scoped to someone else? A connection created as “only me” is invisible to everyone else, and to Agent Apps.