Skip to main content
Rippit works with any client that speaks MCP over Streamable HTTP with OAuth. The clients below are the ones we have set up and tested; see Any MCP client if yours isn’t listed.

​
Choosing where to start

If your organization standardizes on one assistant, Claude and ChatGPT split into separate admin and end-user pages. Do the admin page first, then send your team the end-user page directly. If developers want it in their editor or terminal, Claude Code, Codex, Cursor, and Gemini CLI are per-developer setups with no admin step; each person adds it themselves. If your client isn’t listed, it very likely still works. Rippit supports OAuth 2.1 dynamic client registration, so an unknown client can register itself and connect with nothing more than the server URL. See Any MCP client.

​
What every client has in common

  • The endpoint is always https://mcp.rippit.com/mcp.
  • Sign-in always happens in a browser at app.rippit.com. You never enter Rippit credentials into your assistant.
  • Access is always scoped to the signed-in user’s existing Rippit permissions.
  • No client secret or API key is needed. If a setup form asks for one, leave it blank.
Charts and interactive Ask Rippit cards only render in clients that support MCP UI cards, which today means Claude. Other clients receive the same answers as text and data.

​
Rippit as a client

This page is about clients connecting to Rippit. Rippit also works the other way: its in-app agent is an MCP client, so you can connect your own servers to it and use them alongside your conversation data. See Rippit Agentic Chat.