> ## 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.

# Troubleshooting

> Common issues with the Rippit MCP connector in Claude.

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.

## 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

1. Try signing in to Rippit again from Claude's settings.
2. If that doesn't help, remove the Rippit connector and add it again.
3. If you still can't get in, your organization may not be enrolled in the private beta yet.

<Info>
  **Admin help needed for step 3.** Contact your Rippit point of contact to confirm beta enrollment for your organization.
</Info>

## 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](/user-guide#feedback)) 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.

<Info>
  **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.
</Info>

## Charts or images in the answer aren't loading

Your browser or company network might be blocking one of Rippit's hosts.

<Info>
  **Admin help needed.** Ask your IT admin to check that `cdn.rippit.com` is allowed through any browser extensions or corporate proxies.
</Info>

## Disconnecting Rippit

Remove the Rippit MCP entry from Claude's connector settings. This discards the tokens stored locally.

<Info>
  **Admin help needed if you suspect a token leak.** Contact Rippit support so we can invalidate the refresh token server-side.
</Info>

## Streamable HTTP Error

If you get this error (full error code below), disconnect the Rippit connector, reconnect, and re-authenticate.

`Streamable HTTP error: Error POSTing to endpoint: {"type":"error","error":{"type":"authentication_error","message":"OAuth token has been invalidated. Re-authentication is required.","details":{"error_code":"mcp_invalid_oauth_token"}},"request_id":"req_011CbA8oiM372U7xD2MADDpM"}`

## Installing the Rippit MCP in Cursor

You can also connect Rippit to Cursor as a custom MCP server.

1. Open **Cursor Settings** (`Cmd/Ctrl` + `,`, or the gear icon in the top-right).
2. In the left sidebar, select **Tools & MCPs**.
3. Under **Installed MCP Servers**, click **New MCP Server** ("Add a Custom MCP Server"). This opens your `mcp.json` configuration file.
4. Add the Rippit entry to `mcpServers`:

```json theme={null}
{
  "mcpServers": {
    "Rippit": {
      "url": "https://mcp.rippit.com/mcp",
      "auth": {
        "CLIENT_ID": "cursor-mcp"
      }
    }
  }
}
```

5. Save the file. Rippit appears under **Installed MCP Servers** — toggle it on if it isn't already.
6. When prompted, sign in to Rippit in the browser window that opens to finish authenticating.

<Info>
  Make sure **Wait for MCP Authentication** is enabled in **Tools & MCPs** so Cursor waits for you to complete sign-in rather than timing out.
</Info>