AI tools

Rippit in your AI tools

Connect Rippit to Claude, ChatGPT, Gemini, Copilot and more, so you can ask about your customers and your business from the assistant you already use.

Nothing to installOne server URL for every assistant

Your own accessEach person signs in and sees only what they can see in Rippit

Your tools stay untouchedRippit only creates worksheets in Rippit, never in other tools

How it fits together

Your AI assistantClaude, ChatGPT, Gemini and more

RippitReads your data and answers

Your answerWith the full conversations behind it

The server URL

The same for every assistant. There’s no API key, client secret or token. If a setup form asks for one, leave it blank.

https://mcp.rippit.com/mcp

How setup works

1
An admin adds Rippit once
For your organization or workspace in the assistant. This on its own gives no one access to data.
2
Each person signs in
The first time they use it, with their own Rippit account. The assistant acts as that person and sees only what they can already see in Rippit.

Name Rippit in your prompt

Say “Use Rippit to…” so the assistant picks it. Ask for a judgment, not a tag count, and add new AI columns instead of forcing answers from existing ones.

Set it up in your assistant

Charts and interactive Rippit cards show in Claude. Other assistants get the same answers as text and data.

ClaudeWeb and desktop, including CoworkAn org admin adds it, then each person connects

Before you start Each person needs their own Rippit account.

Admin

1
Open connectors
In Claude, go to Settings > Connectors and click Add custom connector.
2
Add Rippit
Name it Rippit, paste https://mcp.rippit.com/mcp, and click Add.
3
Test before announcing
Adding the connector gives no one access to data. Have one person connect and try it first.

Each person

1
Connect
Go to Settings > Connectors (you may land on Customize), find Rippit and click Connect.
2
Sign in
Sign in at app.rippit.com and approve.
3
Use it
Check that the connector shows as active. Optionally set the Rippit tools to Always Allow, then name Rippit in your prompt, like “Use Rippit to show me the top drivers of contact volume last month.”

Good to know

If Rippit isn’t in the list, the admin step isn’t done yet.
Charts and interactive Rippit cards render in Claude. Other assistants get the same answers as text and data.
Claude Code is set up separately.

Claude CodeTerminalEach developer

Set up

1
Add the server
Run the command below.
2
Sign in
Launch claude, type /mcp, select rippit, then Authenticate. Sign in in the browser and approve.

Add Rippit

claude mcp add --transport http rippit https://mcp.rippit.com/mcp

Check it worked Run /mcp again and check that Rippit shows as connected.

Good to know

On SSH or cloud machines, open the printed sign-in link in a browser on your own computer.
Connectors aren’t shared with the Claude apps.

ChatGPTWeb and desktopA workspace admin or owner adds it, then each person connects

Before you start ChatGPT Business, Enterprise or Edu. Not available on Free, Plus or Pro.

Admin

1
Turn on Developer mode
Settings > Security + Login > Developer mode. This is a personal setting.
2
Create the app
Workspace Settings > Apps > Create. Name: Rippit. MCP server URL: https://mcp.rippit.com/mcp. Authentication: OAuth. Leave client ID and secret blank.
3
Check the tools load
Run the tool scan. If no tools appear, the URL is wrong or unreachable.
4
Test it
Click Connect and sign in at app.rippit.com. In a new chat, pick Rippit from the + menu and ask “List my Rippit data sources.”
5
Publish
Publish the app and install it for everyone. Enterprise and Edu can limit it by user, group or action. Have one non-admin try it before announcing.

Each person

1
Connect
Profile > Settings > Plugins (or Apps, or Apps & Connectors). Click Rippit, then Connect, and sign in.
2
Pick Rippit in each chat
Under the composer in a new chat, or from the + menu in an existing one. ChatGPT only uses Rippit when it’s selected.

Check it worked The test question in the admin steps returns your real data.

Good to know

On Business, a published app can’t be edited. Any change means recreating and republishing, so get the test working first.
When Rippit adds tools, use Refresh in the app settings (republish on Business).
A consent screen saying “unverified” with self-reported details is expected.
A toggle showing Rippit as on isn’t the same as connected. You still need to click Connect.
The desktop app’s coding view is set up through Codex.

CodexCLI, ChatGPT desktop app and IDE extensionEach developer

CLI

1
Add the server
Add the config below to ~/.codex/config.toml.
2
Sign in
Run codex mcp login rippit, then sign in at app.rippit.com and approve.

Desktop app

1
Add the server
Settings > MCP servers (under Connections in recent versions) > Add server. Choose Streamable HTTP and paste https://mcp.rippit.com/mcp.
2
Sign in
Save, Restart, then Authenticate and sign in.

~/.codex/config.toml

[mcp_servers.rippit]
url = "https://mcp.rippit.com/mcp"
auth = "oauth"

Check it worked codex mcp list shows Rippit.

Good to know

The CLI, desktop app and IDE extension share one config, so adding Rippit in one adds it to all three.
Don’t set bearer_token_env_var. It blocks sign-in.
This doesn’t add Rippit to ChatGPT chats.

Microsoft CopilotCopilot StudioThe agent builder adds it, then each person approves in chat

Set up

1
Add a tool
On the agent’s Tools page: Add a tool > New tool > Model Context Protocol.
2
Fill in the server
Server name: Rippit. Description: one sentence on what Rippit does (Copilot reads it to decide when to use Rippit). Server URL: https://mcp.rippit.com/mcp.
3
Choose sign-in
Authentication: OAuth 2.0. OAuth type: Dynamic discovery (not Dynamic or Manual).
4
Connect
Click Create, then Next. On Add tool, click Create a new connection, then Add to agent.
5
Add instructions
Recommended: give the agent instructions for using Rippit, so it doesn’t stop to ask people how to filter or group.

Check it worked Each person sees a consent card in chat the first time.

Good to know

Streamable HTTP only. Older guides that use SSE don’t apply.
Your Power Platform data policies apply and can block the connection.
Microsoft 365 Copilot declarative agents use the M365 Agents Toolkit with the same server URL.

Gemini EnterpriseA Google Cloud admin and a Gemini Enterprise admin, then each person signs in

Set up

1
Allow the traffic
A Google Cloud admin allows outbound traffic to mcp.rippit.com and app.rippit.com, plus Google’s other custom server prerequisites. Do this first.
2
Add a custom server
Use the settings below. The client ID must match exactly.
3
Turn on tools
Once connected, reload custom actions and turn on the tools you want. People sign in with their own Rippit account the first time.

Settings

Server URL:        https://mcp.rippit.com/mcp
Transport:         Streamable HTTP
Authentication:    OAuth 2.0
Client ID:         gemini-enterprise-mcp
Client secret:     (blank)
Authorization URL: https://app.rippit.com/oauth/authorize
Token URL:         https://app.rippit.com/oauth/token
Scopes:            mcp offline_access
PKCE:              on

Good to know

A client ID made anywhere else causes an invalid_redirect_uri error.
Leave the secret blank. Gemini doesn’t send one with PKCE on.
Agents are limited to 100 tools.
For click-by-click menus, ask your Rippit contact.

Gemini CLITerminalEach developer

Set up

1
Add the server
Run the command below, or add the JSON to ~/.gemini/settings.json (for you) or .gemini/settings.json (for a project).
2
Sign in
Run /mcp auth rippit, then sign in at app.rippit.com and approve.

Add Rippit

gemini mcp add --transport http rippit https://mcp.rippit.com/mcp

settings.json

{
  "mcpServers": {
    "rippit": {
      "httpUrl": "https://mcp.rippit.com/mcp",
      "authProviderType": "dynamic_discovery"
    }
  }
}

Check it worked /mcp auth lists servers that still need sign-in. Rippit shouldn’t be on it.

Good to know

Use httpUrl, not url. url is for SSE, which Rippit doesn’t use.
Sign-in needs local port 7777 free.
If your sign-in expires, run /mcp auth rippit again.

CursorEach developer

Set up

1
Open MCP settings
Settings (Cmd/Ctrl + ,) > Tools & MCPs > Installed MCP Servers > New MCP Server. This opens mcp.json.
2
Add Rippit
Add the JSON below, save, and toggle Rippit on.
3
Sign in
Sign in when the browser opens.

mcp.json

{
  "mcpServers": {
    "Rippit": {
      "url": "https://mcp.rippit.com/mcp"
    }
  }
}

Good to know

Turn on Wait for MCP Authentication in Tools & MCPs so Cursor doesn’t time out during sign-in.

NotionCustom AgentsA workspace admin turns it on, then an agent editor connects it

Before you start Notion Business or Enterprise.

Workspace admin

1
Allow custom servers
Settings > Connections > Manage > Enable custom MCP servers.
2
Approve Rippit if needed
If members can only use approved connections: Approved connections > Add approved connection > Custom MCP server, paste https://mcp.rippit.com/mcp, and Save.

Agent editor

1
Add the connection
In the Custom Agent: Settings > Tools & Access > Add connection > Custom MCP server. Paste https://mcp.rippit.com/mcp and name it Rippit.
2
Sign in
Choose OAuth, leave client ID, secret and API key blank, click Connect and sign in.

Good to know

The sign-in belongs to one agent and uses the connecting person’s Rippit account. Everyone who chats with that agent gets that person’s access.
Only the person who connected Rippit can change which tools run automatically.

PerplexityEach person, or an Enterprise admin for the whole org

For yourself

1
Add a connector
Sidebar > Plugins (older layouts: Customize > Connectors) > Add custom > Connector > Add MCP connector > Remote.
2
Fill it in
Name: Rippit. Server URL: https://mcp.rippit.com/mcp. Authentication: OAuth 2.0. Transport: Streamable HTTP. Leave client ID and secret blank. Check the box and click Add.
3
Sign in
Click the Rippit card and sign in. Finish before closing the tab.

Enterprise admin

1
Add it for the org
Enterprise settings > Permissions > Connectors permissions > + Custom connector > Remote, with the same values.
2
Share it
Share it with the org from Permissions. It can take a while to show up for members.
3
Optional
To let members add connectors themselves: Enterprise settings > Connectors > Connector permissions > Allow members to add custom connectors.

Good to know

Each person should sign in with their own Rippit account, not a shared one.

n8nWorkflowsThe workflow builder

Set up

1
Add the tool
In the AI Agent node, add a tool and choose MCP Client Tool.
2
Fill it in
Endpoint: https://mcp.rippit.com/mcp. Server Transport: HTTP Streamable. Authentication: MCP OAuth2.
3
Sign in
Create a credential, leave Use Dynamic Client Registration on and the rest blank, then click Connect my account.
4
Pick tools
Under Tools to Include, keep All or choose Selected.

Good to know

Every run, including scheduled ones, acts as the person who signed in.
If runs start failing at sign-in, click Connect my account again.

RunlayerA Runlayer admin, then each person signs in once

Admin

1
Create the connector
Manage connectors > Add connector > Create New. Name: Rippit. URL: https://mcp.rippit.com/mcp. Transport: Streaming HTTP. Authentication: OAuth 2.1 (or Auto). No client ID or secret.
2
Make it available
Add Rippit to your Runlayer Plugin or approve it under policies.

Each person

1
Add to your assistant
Open the Rippit connector, click Add to Client, and follow the steps for your assistant.
2
Sign in
In Claude and ChatGPT, a sign-in link appears on your first request. Sign in, then ask again. Cursor, VS Code and Codex open sign-in automatically.

Any other assistantAny client with Streamable HTTP and OAuthDepends on the client

Before you start The client must support Streamable HTTP and OAuth 2.1 sign-in with PKCE.

Set up

1
Add the server
Server URL: https://mcp.rippit.com/mcp. Transport: Streamable HTTP. Auth: OAuth 2.0 or 2.1.
2
Leave keys blank
No client ID, secret, API key or token. The client registers itself.
3
Connect and sign in
The client finds Rippit’s sign-in settings automatically and opens the browser.

Check the server is up

curl -si -X POST https://mcp.rippit.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"initialize","id":1}' | grep -i www-authenticate

Check it worked A 401 with a WWW-Authenticate header pointing to /.well-known/oauth-protected-resource means the server is up. It doesn’t confirm your client is connected.

Good to know

SSE isn’t supported.
A registration is discarded after 1 hour if sign-in isn’t finished.
For help, email team@rippit.com with the client name and the exact error.

What your assistant can do

14 tools. Rippit can turn on more for your workspace. Nothing is ever written to your helpdesk or other connected tools.

Tool	What it does	Access
list_data_sources	Lists the tables you can query. Usually the first call	Read
list_worksheets	Lists your saved worksheets	Read
describe_table	A table’s columns, types, values and how far back the data goes	Read
describe_column	One column’s type, description and distinct values	Read
read_table	Reads rows, with filters, chosen columns and paging	Read
aggregate_table	Groups rows and counts, sums or averages them	Read
pivot_table	A cross-tab with row and column totals	Read
read_conversations	Full transcripts by ticket ID	Read
get_enrich_status	Waits for an AI column job and reports progress	Read
ping	Checks the server is reachable and you’re signed in	Read
create_worksheet	Saves a filtered slice of a table as a worksheet, ready for AI columns	Creates in Rippit
enrich_worksheet	Adds AI columns that classify, score or pull a judgment from each conversation	Creates in Rippit
upload_csv	Opens a picker to upload a CSV or Parquet file as a worksheet	Creates in Rippit

Troubleshooting

The connector turns red right after signing in

Usually a stale saved sign-in. Remove the connector and add it again.

You see an error or can’t sign in

Sign in again from your assistant’s settings, then remove and re-add the connector. If it still fails, your organization may not have access yet. Contact your Rippit contact.

The sign-in page doesn’t open

On a remote machine, SSH or a cloud workspace, copy the sign-in link into a browser on your own computer.

Rippit doesn’t respond

The assistant didn’t pick Rippit. Name Rippit in your prompt.

Tool calls keep failing

Sign in again. An admin can check the server at https://mcp.rippit.com/.well-known/oauth-protected-resource. A 200 with JSON means the server is fine and the problem is on the assistant’s side. A 404 or timeout means it can’t be reached.

Charts or images don’t load

A browser extension or proxy is blocking cdn.rippit.com. Ask IT to allow it.

“OAuth token has been invalidated” (mcp_invalid_oauth_token)

Disconnect, reconnect and sign in again.

You need to disconnect

Remove Rippit from your assistant’s connector settings.

Security

How sign-in, access and logging work for Rippit in your AI tools: Security.

Your data and creativity is your edge. Put agents on it to maximize it.

Connect your data. Launch agents.

Start free →Book a demo

The server URL

How setup works

An admin adds Rippit once

Each person signs in

Set it up in your assistant

Admin

Open connectors

Add Rippit

Test before announcing

Each person

Connect

Sign in

Use it

Good to know

Set up

Add the server

Sign in

Good to know

Admin

Turn on Developer mode

Create the app

Check the tools load

Test it

Publish

Each person

Connect

Pick Rippit in each chat

Good to know

CLI

Add the server

Sign in

Desktop app

Add the server

Sign in

Good to know

Set up

Add a tool

Fill in the server

Choose sign-in

Connect

Add instructions

Good to know

Set up

Allow the traffic

Add a custom server

Turn on tools

Good to know

Set up

Add the server

Sign in

Good to know

Set up

Open MCP settings

Add Rippit

Sign in

Good to know

Workspace admin

Allow custom servers

Approve Rippit if needed

Agent editor

Add the connection

Sign in

Good to know

For yourself

Add a connector

Fill it in

Sign in

Enterprise admin

Add it for the org

Share it

Optional

Good to know

Set up

Add the tool

Fill it in

Sign in

Pick tools

Good to know

Admin

Create the connector