Issues end users and admins might run into when using the Rippit MCP connector in Claude. Items flagged with Admin help needed require action from whoever installed the connector for your organization, or from Rippit support.Documentation Index
Fetch the complete documentation index at: https://docs.rippit.com/llms.txt
Use this file to discover all available pages before exploring further.
The connector goes red right after sign-in
There’s likely a stale token cached from a previous connection. Remove the Rippit connector and add it again so it runs a fresh sign-in.I’m getting an error or can’t sign in
- Try signing in to Rippit again from Claude’s settings.
- If that doesn’t help, remove the Rippit connector and add it again.
- If you still can’t get in, your organization may not be enrolled in the private beta yet.
Admin help needed for step 3. Contact your Rippit point of contact to confirm beta enrollment for your organization.
The sign-in screen didn’t open in my browser
If you’re using Claude on a remote machine (over SSH or a cloud workspace), it can’t open a browser locally. Your app should print a sign-in link in the terminal or chat — copy that into a browser on your own computer to finish signing in.Rippit isn’t responding to my questions
Mention Rippit explicitly in your prompt — for example, “Use Rippit to list my workbooks.” Most agents need that nudge to pick the right tool.My analysis seems stuck
Ask Rippit answers can take a couple of minutes for complex questions, so a long-running card isn’t always stuck. If nothing changes for more than a few minutes, dismiss the card and ask the question again. If it stalls a second time, send feedback (see User Guide) and include roughly when it happened.Tool calls keep failing
Sign in to Rippit again from Claude’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; the problem is on the client side. A 404 or timeout means the server itself is unreachable.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.Disconnecting Rippit
Remove the Rippit MCP entry from Claude’s connector settings. This discards the tokens stored locally.Admin help needed if you suspect a token leak. Contact Rippit support so we can invalidate the refresh token server-side.